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

With no annotations, the description carries the full burden and discloses one important behavior: paid verdicts are refused over MCP and must be retrieved via x402 on GET /receipt. However, it omits other relevant traits such as whether the tool is read-only, what it returns for non-paid receipts, and any authentication or rate-limit behavior.

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?

The description is a single, short sentence with two clauses and no filler. The purpose clause is front-loaded, though the second clause is cryptic and could have been clearer.

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 tool with no annotations, no output schema, and zero schema description coverage, the description is too thin. It mentions an x402/MCP payment constraint but does not fully explain the tool's behavior, return values, or parameter semantics.

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%, so the description must compensate for the undocumented receipt_id parameter. It never explains the format, source, or meaning of receipt_id, adding no semantic value beyond the parameter name.

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 says it 'Explains the paid receipt-query path,' which suggests documentation rather than a query operation, yet the input schema requires a receipt_id. It does not clearly state what the tool returns or distinguish it from sibling tools such as annsurv_verify_receipt.

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 notes that paid verdicts are refused over MCP and deliver over x402 on GET /receipt, which is a usage constraint, but it gives no explicit guidance on when to use this tool versus alternatives like annsurv_verify_receipt or annsurv_check.

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