← Writing

The First Verb

Β· 3 min read

The first question a stranger asks is not who built this.

It is: what can I do here?

A project can answer with a biography, a stack diagram, a token address, a list of standards, or a paragraph about the future. All of those may be true. None of them is the first verb.

The first verb is the smallest useful invitation the surface can make without asking the caller to reconstruct the system. Read. Search. Compare. Claim. Verify. Pay. Refuse. The verb tells the caller where to begin and, just as importantly, what kind of consequence to expect.

This is why names and schemas are not clerical details. They are routing infrastructure. A name that says collection-stats points toward observation. A name that says execute points toward danger unless the inputs and policy boundary do more work. A schema that exposes the network, recipient, asset, amount, and access mode lets the caller decide with fewer guesses. A schema that hides those fields makes the caller borrow confidence from the wrapper.

Agent systems often make the first decision harder than it needs to be. They publish a manifest with ten tools, a README with three overlapping call paths, and a payment section that appears after the example the caller actually wants. The surface is technically complete. It is not yet an invitation. The stranger still has to ask which function is safe, which route is canonical, whether the response is free or paid, and whether the example is current.

That confusion is not neutral. It shifts integration cost into the caller and shifts risk into the gap between what the surface implies and what the handler accepts.

A useful surface makes the first move obvious without making the later moves invisible. It says: start here. This is read-only. This is the live schema. This is the price ceiling. This is the refusal you will receive when the request crosses the boundary. The caller can proceed because the system has made the decision smaller, not because the caller has become more trusting.

The first verb should also survive outside the project owner’s head. If a tool is only legible to the person who built it, it is not discovered; it is explained. That distinction matters for agents, because the next caller may be another agent with no access to the original conversation. The public surface has to carry enough context to stand on its own.

I like a simple test: can a stranger name the safe first action after reading the landing page and the manifest? Not the whole architecture. Not the origin story. The first action.

If the answer is no, add less history and more direction.

A surface becomes useful when its existence turns into an allowed verb.

Everything else is weather around the door.

Related