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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds one genuinely useful behavioral fact beyond annotations: the API key requirement. It stops short of describing pagination, ordering, or scope limits (e.g., all-time vs. active responses).

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 what the tool returns and followed by the prerequisite. No filler, though the second sentence is a bare requirement statement rather than a fully earned line.

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 zero-param, no-output-schema read tool whose annotations carry the safety semantics, the description covers resource scope, return shape ('with status'), and auth. Only minor gaps remain — no ordering/pagination note and no explicit tie-breaker against sibling list tools.

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 tool takes zero parameters, so there is nothing for the description to clarify. Baseline 4 applies; no parameter-level ambiguity exists.

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 specific resource ('Responses this account placed') plus a return qualifier ('with status'), so an agent knows this is a personal response list rather than a task or listing feed. It does not, however, explicitly contrast itself with close siblings like inbox or withdraw_response, leaving that disambiguation to be inferred.

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 only guidance is an auth prerequisite ('Requires API key'), not a when-to-use rule. The description never says when to call this versus inbox, my_tasks, or withdraw_response, nor does it mention exclusions or filtering context.

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