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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context with 'one row per generation attempt', which clarifies that multiple rows can exist for the same report and that the output is history rather than a single status. Minor unspecified behaviors like ordering or inclusion of failed attempts are not disclosed, but the description adds meaningful value beyond the annotations.

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 concise sentence with the core action and resource front-loaded. 'One row per generation attempt' earns its place by preventing a common misconception that exports are deduplicated. There is no wasted prose.

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 read-only list operation with one parameter, a complete schema, and an output schema, the description is sufficiently complete. The combination of a clear scope, the per-attempt row semantics, and annotation-covered safety gives an agent everything needed to invoke the tool correctly. No significant contextual gap is evident.

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% and the report_id parameter is already described as coming from list_reports, so the schema carries the parameter semantics. The description does not add additional parameter-level detail, which matches the baseline for high schema coverage.

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 states a specific verb ('List') and a specific resource ('PDF export history for a report'), and clarifies that each generation attempt appears as its own row. This makes it clear how the tool differs from related siblings like generate_pdf or get_pdf_status, which create or check individual exports.

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 given about when to use this tool versus alternatives such as generate_pdf, get_pdf_status, or archive_export. The only contextual hint is the parameter description's reference to list_reports, which suggests where the report_id comes from, but there is no explicit when-to-use or when-not-to-use guidance.

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