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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is covered structurally. The description adds real value with 'Permanently' and the consequence that future runs stop firing, but it says nothing about auth requirements, whether the action is reversible, or what happens to already-generated reports.

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 sentence that leads with the destructive verb and immediately states the operational consequence. No filler, nothing to trim.

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 one-parameter destructive tool with annotations covering the safety profile and no output schema, the description covers what it does and its scheduling side effect. It is nearly complete, missing only a note on reversibility or required permissions.

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?

Only one parameter (scheduleId, a UUID) with 0% schema description coverage, and the description never mentions it. The name is fairly self-explanatory, so this is the minimum-viable baseline rather than a gap that genuinely confuses an agent.

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?

States a specific verb+resource ('Permanently delete a recurring report schedule') and clarifies the effect ('stop its future runs from firing'). This clearly distinguishes it from the sibling reports_manage/reports_query tools, though it never names an alternative explicitly.

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?

There is no guidance on when to delete versus when to pause/disable a schedule, and no mention of prerequisites, permissions, or recovery options. The agent is left to infer that this is the terminal action for a schedule.

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