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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds that the record is 'private' (implying authorization) and that a payout receipt is exposed, which is useful but not rich behavioral 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?

A single tight sentence with the read action front-loaded and the two returned artifacts listed economically. No filler, though it is perhaps too terse to carry usage guidance.

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 read-only tool with no output schema, the description does name the returned content (review state, payout receipt), which is helpful. However, it omits when to call it, the auth requirement, and any error/absence behavior, leaving gaps for an agent working across ~100 siblings.

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 50%: agent_key is fully documented in the schema (including the Bearer alternative and the never-publish warning) while claim_id carries only a pattern. The description adds no format or auth detail for either parameter, so it merely gestures at claim_id via 'your private ... claim'.

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?

States a concrete verb (Read) and resource (market-service campaign claim), plus what it returns (review state and payout receipt). It is clearly the read-side counterpart to speedbot_claim_market_service, but it never names or differentiates itself from that sibling explicitly.

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?

Usage is only implied: the 'private ... claim' framing suggests it is called after a claim exists to check status. There is no statement of when to use this versus speedbot_claim_market_service or speedbot_market_service_task, and no prerequisites given.

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