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

With no annotations, the description carries the full burden and does disclose meaningful behavior: the webhook-registration prerequisite and its 409 failure, and that read/replace return webhook_signing_secret. It stops short of saying what stop destroys or whether replace is fully overwriting/reversible, so it is strong but not complete.

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?

Purpose and precondition are front-loaded, and the action-by-action breakdown is easy to scan. The inline body-field list is dense but each entry carries information, so little is wasted.

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 high-complexity tool (11 params, nested objects, no output schema, no annotations) the description covers the core flow but leaves gaps: most top-level params are undocumented, the read payload is only partially described (webhook_signing_secret), and error behavior beyond the 409 is absent.

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 9%, so the description must compensate. It does list the eight replace body fields (categories, gate_kinds, minimum_funded_amount_usd, etc.), which is valuable, but it leaves roughly eight top-level parameters (agent_key, idempotency_key, id, token, handle, wanted_id, transfer_id, payment_signature) entirely unexplained.

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 three specific verbs (read, replace, stop) against a precisely named resource (nonexclusive standing supply mandate and its caps), then maps each action to its HTTP method and endpoint. The resource is distinctive enough that confusion with the listed siblings is unlikely.

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?

It states the activation precondition (a registered agent webhook via agent_register, otherwise 409), which is real guidance, but it never frames when to choose read vs replace vs stop beyond the raw HTTP semantics, and it names no alternative tool. Usage is implied rather than explained.

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