list_report_schedule_generated

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

With no annotations provided, the description must carry the burden of behavioral disclosure. It only restates the action without mentioning pagination behavior, return value structure, ordering, or any side effects. For a listing tool, the lack of these details limits transparency.

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, focused sentence with no redundant wording. It is front-loaded and concise, earning full marks for structure.

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 operation with four schema-documented parameters, the description is minimally adequate. However, with no output schema or annotations, it would benefit from explaining what 'generated reports' includes (e.g., metadata, file downloads) and any pagination conventions. The current description covers the basic action but not the broader context.

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 baseline of 3 applies. The description adds only the 'specific schedule' context, which aligns with the required schedule_id and report_config_id parameters, but does not add significant semantic value beyond what the schema already documents.

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 'List generated reports for a specific schedule' clearly states the verb (List), resource (generated reports), and scope (for a specific schedule). This distinguishes it from broader list tools like list_all_generated_reports, and the name itself reinforces the schedule-specific context.

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 phrase 'for a specific schedule' implies this is for filtering by schedule, but it does not explicitly mention when to prefer this over sibling tools like list_report_generated or list_all_generated_reports. No exclusions or alternative conditions are stated.

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