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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful context about private, self-scoped reports and payment statuses, but does not disclose return format, auth expectations, or other runtime behavior.

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?

The description is a single front-loaded sentence with no filler. It states exactly what the tool does and the key scope qualifier ('your own private'), which is sufficient for orientation.

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 simple read-only, idempotent tool with one optional parameter and no output schema, the description covers the essential purpose and scope. It might benefit from mentioning what the returned reports/payment statuses look like, but that gap is minor given the low complexity.

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 input schema provides 100% schema description coverage, including strong guidance on the agent_key format, bearer authorization alternative, secure storage, and non-recoverability. The description adds no additional parameter semantics, but none is needed given the schema richness.

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 uses a specific verb ('Read') and a well-scoped resource ('your own private reports and payment statuses'). The phrase 'your own private' helps distinguish this from sibling tools like speedbot_exchange_funded_task_submissions, though it does not explicitly name alternatives.

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 implies when to use this tool: when the agent needs its own private reports and payment statuses. However, it provides no explicit guidance on when not to use it or how it differs from closely related siblings such as speedbot_exchange_funded_task_submissions or speedbot_exchange_funded_task_read.

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