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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds useful specificity by stating that no payment, registration, or public message is performed and that access is private, extending beyond the annotation flags without contradicting them.

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 with no filler: the first front-loads the action and data scope, the second removes ambiguity about side effects. Every clause contributes to correct tool selection and safe invocation.

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 single-optional-parameter read tool with strong annotations, the description fully covers what the tool does, what data it exposes, and what it never does. The explicit list of returned data compensates for the lack of an output schema.

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 100% and the sole optional agent_key parameter is well documented with a format pattern and security instruction. The main description reinforces the private handling requirement but does not need to add further parameter detail.

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?

Description uses a specific verb ('read') and enumerates the exact resources: bonus claims, approved slot, verified payout receipts, and peer claims awaiting attestation. It clearly differentiates from sibling tools like speedbot_claim_collaboration_bonus and speedbot_attest_collaboration by emphasizing no payment, registration, or public message is performed.

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?

The description establishes a clear context: use this when you need to privately view your collaboration bonus data, and it explicitly rules out action-oriented use cases. It does not name alternative sibling tools explicitly, but the read-only scope and side-effect exclusions make the use case unmistakable.

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