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

Annotations already flag destructive=true and idempotent=false, but the description adds real context beyond them: deletion also expires any still-pending delivery, and it explicitly bounds the blast radius by not touching tickets or follows. It does not say what happens when the reminder is already deleted or already delivered, which matters given the non-idempotent hint.

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 short sentences, zero filler, with the action and its scope stated first and the exclusion boundary second. Nothing is redundant with the annotations or schema.

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?

An output schema exists, so return values need not be described, and the destructive side effects and non-effects are covered. The remaining gap is identifying which id to pass and what an already-expired or nonexistent reminder produces, which a caller of a non-idempotent delete would want to know.

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 description coverage is 0% on the single required parameter, so the description was the only place to explain that 'id' is the reminder UUID (presumably from list_reminders) rather than a ticket, follow, or user id. It says nothing about the parameter at all, leaving the agent to infer the identifier type from the name alone.

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 ... your reminder') and immediately delimits scope ('only your reminder ... Does not alter tickets or follows'), so an agent knows this removes a reminder and nothing else. It is clear without opening the schema, though it never distinguishes itself from the sibling delete_alert.

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?

Usage is only implied: the word 'your' and the single id parameter suggest deleting a reminder the caller owns, presumably one obtained from list_reminders. There is no explicit when-to-use versus list_reminders or delete_alert, and no stated precondition such as owning the reminder.

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