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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is supplied structurally. The description adds the consequential detail those hints cannot: the schedule "stops running and cannot be restored," making irreversibility concrete rather than abstract. It stops short of stating permission requirements or whether run history is preserved.

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, with the consequence and irreversibility front-loaded ahead of the alternative. Every sentence earns its place: what it does, what it destroys, and where to go instead.

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 whose annotations already flag destructiveness and idempotency, the definition covers action, permanence, and the correct alternative, so nothing essential to invoking it correctly is missing. Minor gaps remain around auth requirements and whether output is returned, though a delete operation likely needs none.

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?

There is a single required parameter with 100% schema description coverage, and the schema already explains that the id comes from schedule_request or list_schedules. The description adds nothing about the id beyond that, so the baseline of 3 applies since the schema carries the full burden.

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 scheduled request") plus the permanence qualifier "for good," and explicitly names the sibling pause_schedule as the non-destructive counterpart. An agent can distinguish it from get_schedule, pause_schedule, and resume_schedule without opening any 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?

Provides an explicit alternative and the condition that selects it: "To stop it for a while, use pause_schedule." This is exactly the routing decision an agent faces among the schedule siblings, so the when-to-use/when-not guidance is complete for the realistic ambiguity.

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