Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full behavioral burden and falls short. It doesn't state that auth is required (wallet/nonce/signature), what happens to the original offer after a counter (voided? superseded?), whether the counter is binding or reversible, or any rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

A single tight sentence with no filler, front-loading the action. It is efficient, though it is arguably too terse given the tool's auth complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a signed, mutating tool with no annotations, no output schema, and mostly undocumented parameters, the description omits the auth flow and the fate of the original offer. An agent would need external context to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 38% across 8 parameters. The description loosely maps to price, currency, and eta_hours, but says nothing about the four required parameters (offer_id, wallet, nonce, signature) or note, so it does not compensate for the schema gap on this signed mutation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (counter) and resource (an open offer), and names the mutation being made (new price/token/ETA). It is distinguishable from accept_offer and make_offer by the word 'counter', though it never explicitly contrasts itself with them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only usage signal is 'an open offer from the other party', which implies the precondition but does not spell it out. There is no guidance on when to counter versus accepting the offer, making a fresh offer, or walking away, and no mention of prerequisites such as needing an active offer_id.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.