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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so 'Read-only' merely repeats structured data. The genuinely additive item is 'Free, 0 credits,' which discloses cost behavior an agent cannot see in the annotations, but nothing is said about result count, ordering guarantees, or defaults.

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?

Three short fragments, front-loaded with the resource and its URLs, then cost, then safety. Nothing is padded, though the fragmentary style omits any connective guidance that could have earned its place.

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 does cover the return shape (reports/teardowns with URLs), and annotations cover safety. However, for a paginated list tool the missing default limit, result count, and auth expectations leave real gaps.

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 0% for the single 'limit' parameter (max 50, no default documented). 'Your most recent' weakly implies recency ordering, but the description never explains the limit, its default, or the 50 cap, so it fails to compensate for the schema gap.

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 names the concrete resource returned: the user's most recent pitch reports and teardowns, including their URLs. That is specific enough to distinguish a listing tool from the sibling creation tools pitch_report and teardown, though the verb 'list' is only implied rather than stated.

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?

'Your most recent' implies retrieval of previously generated reports, which hints at when to use it, but there is no explicit when-to-use statement and no sibling is named as an alternative. The agent must infer that this is the read counterpart to pitch_report/teardown.

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