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

No annotations are provided, so the description carries full burden for behavioral disclosure. It mentions that reports are automatically generated and emailed, which describes scheduled reports themselves, not the listing operation's behavior (e.g., read-only, return format, pagination). This is insufficient for 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 two concise sentences, front-loaded with the primary action and scope, and contains no fluff or repetition.

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, no-parameter list operation, the description provides enough context: it lists all reports for the team and notes the cadence. Lacking output schema, it could be more specific about return fields, but the complexity is low, so this is acceptable.

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 input schema has zero parameters, so the description has no responsibility to explain parameters. Baselines for 0 params is 4.

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 all scheduled reports for the team, using a specific verb ('List') and resource ('scheduled reports'). It is distinct from sibling tools like create/update/delete_scheduled_report and other list_* tools by specifying 'scheduled reports'.

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 implies use case: when you need to see all scheduled reports. It doesn't explicitly mention when not to use or alternative tools, but context makes it clear. Since no other list_scheduled_reports exists, this is sufficient.

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