list_debug_reports

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

The description discloses that the tool lists all stored debug reports, which is a clear read-only behavior. However, without annotations, it does not mention return format, pagination, ordering, or any potential side effects. It is honest but minimal, adding no context beyond what the sentence itself says.

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, succinct sentence that front-loads the action ('List all') and the resource. Every word contributes, with no fluff or redundancy.

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, zero-parameter list tool without an output schema, the description sufficiently conveys what it does. It is complete enough for the agent to understand the operation, though it leaves 'metadata' unspecified and does not describe the expected output structure. These are minor gaps given the tool's simplicity.

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 has zero parameters and an empty input schema, so schema coverage is trivially 100%. No additional parameter description is needed, and the baseline for zero parameters is 4. The description adds no param-specific info, but none is required.

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 the specific verb 'List' and clearly identifies the resource as 'all stored debug reports' with 'metadata', distinguishing it from siblings like get_debug_report (specific retrieval) and clear_old_reports (deletion). The scope ('all') is explicit, making the tool's purpose unambiguous.

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 gives no explicit guidance on when to use this tool versus alternatives. While it is implicitly separate from get_debug_report, it does not state 'use this to browse all reports' or mention any restrictions or prerequisites. There is no when-to-use or when-not-to-use context.

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