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

Discloses the destructive nature ('permanently delete') and the confirm requirement. No annotations are provided, so the description carries full burden; it could mention irreversibility or side effects but does not.

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?

Two sentences, no superfluous words. The first sentence states the action and resource, the second adds the critical requirement. Front-loaded and 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?

Covers the purpose and the confirm requirement but lacks context on prerequisites (e.g., ownership, permissions), error behavior, and response format. With no output schema, some guidance on the return value would improve completeness.

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 coverage is 100%, so baseline is 3. The description does not add meaning beyond the schema for 'id' or 'idempotency_key', and for 'confirm' it largely repeats the schema description. No additional parameter insight is offered.

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?

Clearly states the action 'permanently delete' and the resource 'scheduled report definition'. Distinguishes from sibling tools like create_scheduled_report, update_scheduled_report, and list_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?

Provides a key usage guideline: requires confirm=true to proceed. However, it does not explicitly mention when not to use this tool or compare to other deletion tools, though the name makes the scope clear.

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