list_reports

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

With no annotations, the description carries the full burden. It states 'List' which implies a read operation, but it does not disclose important behaviors such as whether results are sorted, whether the default page size is 50, or whether any filtering is implied. The optional pagination is mentioned but not elaborated.

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?

A single, front-loaded sentence with no extraneous words. Every word contributes to the core meaning, making it highly efficient.

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 list tool, the description lacks critical context: no output schema, no mention of what fields are returned, and no indication of prerequisites (e.g., whether reports must be generated first). Given the sibling tools, more context would help an agent know when to invoke this tool and what to expect.

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%, so the schema fully documents the size and index parameters. The description adds minimal value beyond hinting at 'optional pagination' but does not introduce new meaning or constraints.

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 clearly states the tool lists generated reports, which is a specific verb+resource combination. It distinguishes itself from siblings like generate_report and get_report_status, though it could be clearer about what constitutes a 'generated report'.

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?

No guidance is provided on when to use this tool vs alternatives. There are many list_* siblings, and the description does not explain scenarios where list_reports is preferred (e.g., enumerating available reports vs checking a specific status).

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