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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description's job is lighter; it adds genuine context by stressing permanence and contrasting it with a reversible pause. It stops short of describing side effects beyond the schedule itself (e.g., run history or linked process state), so not a 5.

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?

Three short sentences, front-loaded with the destructive verb and the permanence warning, then the alternative and the id source. Nothing here is padding.

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?

A single-parameter destructive tool with full schema coverage, destructiveHint already set, and no output schema; the description covers the irreversible nature, the safer alternative, and id provenance. Nothing an agent needs to call it correctly is missing.

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% and the single parameter already carries the note 'Schedule id from list_processes', which the description repeats verbatim. No additional format, constraint, or sourcing detail is contributed beyond the schema, so baseline 3 applies.

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 and resource ('Delete a schedule permanently') and immediately distinguishes the intent from the reversible alternative update_schedule. An agent can tell exactly which sibling to pick without opening either schema.

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?

Gives an explicit when-to-use / when-not-to-use rule ('Prefer update_schedule with enabled=false when the intent is stop it for now') and explains the tradeoff (one click reversible vs. not). It also tells the agent where to obtain the required id.

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