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

Annotations declare idempotentHint=true, destructiveHint=false and readOnlyHint=false, but say nothing about the endpoint being retired. The description supplies that crucial behavioral fact (no reward offered, compatibility-only) that an agent could not infer from the annotations or schema, which is exactly the value-add expected when annotations exist.

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, front-loaded with the deprecation status and closed with the redirect. No filler; every clause carries decision-relevant 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 retired no-op endpoint with no output schema, the description covers what an agent needs: it is dead, and where to go instead. It does not explain why 13 required parameters remain on a no-op call, which is the only meaningful remaining gap.

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?

The schema has 14 parameters, 13 of them required, with only 7% description coverage (essentially just agent_key). The description adds zero information about any parameter, so it does not compensate for the near-total documentation gap; only the deprecation context makes the missing detail less consequential.

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 states precisely what the tool currently is: a deprecated reward-claim endpoint kept callable for compatibility that no longer pays out. It distinguishes itself from the sibling speedbot_earning_opportunities by naming it as the live alternative. It never says what the tool originally did, but for a stub that is not needed to decide whether to call it.

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 gives the operative condition (program ended, no new reward) and points to the correct replacement, speedbot_earning_opportunities, for current availability. The 'do not call this' instruction is implied rather than stated, but the routing guidance is explicit.

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