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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds meaningful behavioral detail: it names exactly what is deleted, says nothing is archived, and confirms there is no undo from either the API or the dashboard. This goes well beyond the annotations and gives the agent a clear safety picture. No contradiction with annotations.

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 front-loaded with the destructive warning and deletion scope, then provides crisp usage guidance and a clear alternative. Every sentence contributes meaningful information; the length is justified by the irreversible nature of the operation.

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 single-parameter destructive tool with strong annotations and no output schema, the description covers what is deleted, irreversibility, recovery impossibility, and exactly when to avoid it. No critical information needed to invoke it safely 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?

There is only one parameter, reminder_id, and the input schema already describes it with 100% coverage. The description does not add parameter-specific semantics, but the baseline of 3 applies because 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?

The description opens with 'DESTRUCTIVE AND IRREVERSIBLE' and states a specific verb and resource: 'Cancelling permanently DELETES the reminder, its escalation steps and its entire delivery history.' It clearly differentiates itself from pause_reminder, so an agent can distinguish this destructive tool from its sibling without ambiguity.

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 gives explicit when-to-use criteria ('only use this when the user explicitly says delete, cancel for good, or stop permanently'), concrete counterexamples ('not right now', 'skip today', 'hold off', 'I'm on holiday'), and routes uncertainty to pause_reminder. This is exemplary decision guidance.

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