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

Annotations already declare a non-read-only, non-destructive, non-idempotent write, so the agent knows this mutates shared ranking state. The description usefully adds why the report matters (honest rankings) and when the tx hash applies, but it omits the consequence of the non-idempotent flag (duplicate reports) and any auth or rate-limit context.

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?

Two short sentences, no filler, with the purpose stated first and the conditional tx requirement second. Nothing could be removed without losing information.

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 5-parameter, 0%-coverage mutation tool with no output schema, the description is too thin. It never explains what endpoint_id refers to, what ms and network mean, or how to choose among the outcome enum, leaving the agent to guess on inputs that directly affect ranking data.

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 carries the full burden, yet it only touches 'tx' conditionally and gestures at outcome. It says nothing about endpoint_id, ms, or network, and does not explain the nine outcome enum values, which are the most consequential input here.

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 pairs a clear verb ('Report') with a specific resource ('how a paid call went') and states the downstream effect ('so rankings stay honest'). It is clearly distinguishable from find_paid_endpoint and list_markets, which are lookup tools, but it never names those siblings to make the contrast explicit.

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?

'Include the payment tx hash when you paid' gives a useful conditional that maps to the required/optional split, implying this is called after completing a paid call. There is no explicit when-not guidance, no statement about whether reports are required or optional, and no mention of how this relates to the sibling tools.

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