Identity Control Proof

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

Annotations already declare readOnlyHint=false, idempotentHint=false and openWorldHint=true, so the description's main added value is the payment context: a remote POST costing 0.20 USD in x402/base/usdc on eip155:8453. That is genuinely useful behavioral context. However it says nothing about what the write actually does, what control_evidence must contain, or what side effects occur.

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?

It is short, but the brevity comes from under-specification rather than economy: the first line merely repeats the tool name, and the second line is metadata. Nothing about the actual operation is front-loaded or explained.

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?

An output schema exists so return values needn't be described, and pricing/route are covered. But for a paid, non-idempotent, open-world write endpoint with four completely undocumented parameters, the definition omits the essential facts an agent needs 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 description coverage is 0% — none of the four parameters (claimer, identifier, control_method, control_evidence) has any description, type detail beyond 'string', or example. The description compensates with zero parameter information, leaving the agent to guess the meaning and format of every input.

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?

The description is essentially the title 'Identity Control Proof' restated, plus a route and price. It never says what a control proof is, what it proves, or what it returns, so an agent cannot distinguish it from siblings like v1_identity_agent_attest or v1_provenance_overlay.

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?

There is no when-to-use, when-not-to-use, or alternative-tool guidance. The only routing signal is the HTTP route and price, which does not tell the agent under what circumstances this tool should be selected over the many identity/provenance siblings.

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