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

Annotations already declare readOnly, idempotent, non-destructive behavior, so the safety profile is covered. The description adds genuine value beyond that by disclosing the returned state machine (claimed -> pending_review -> verified -> paid), the inclusion of the BaseScan tx on paid, and the presence of a reason on rejected/held.

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 sentences, no filler, and the most important information (what the tool returns and the state progression) is front-loaded ahead of the optional-parameter note.

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?

With no output schema, the description carries the burden of explaining returns, and it does so adequately via the state list, tx hash, and rejection reason. Minor gaps remain around the shape of a multi-claim response and whether pagination applies.

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 100%, so the baseline is 3, but the description adds real semantic value by clarifying that claim_id scopes the call to a single claim while omitting it implies a full claim listing. That interpretation is not spelled out in the schema's 'optional bcl_... or bounty id' text.

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?

Names the specific resource (your bounty claims) and enumerates the lifecycle states returned, so the agent knows this is a status lookup on claims rather than a bounty detail fetch. It does not explicitly contrast itself with get_bounty, list_bounties, or claim_bounty, which keeps it just short of a 5.

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?

'Pass claim_id for one claim' implies that omitting it returns all your claims, giving implicit usage guidance. There is no explicit statement of when to use this instead of get_bounty or list_bounties, so usage remains inferred rather than stated.

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