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

Annotations already declare destructiveHint=true, so the description's real value is blast-radius disclosure: it clarifies that only the reminder goes away and nothing a prospect sees is destroyed, which directly softens the scary destructive flag. It stops short of covering the non-idempotent behavior (what happens on a second call for an already-cancelled reminder), which is the one meaningful gap.

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 action and its effect, then the non-effects, then the alternative. Every clause adds decision-relevant information with no filler.

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 delete tool with full annotation coverage and no output schema, the description supplies everything an agent needs: what it does, what it does not touch, and which sibling to use for a different intent. Nothing material 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?

With a single parameter at 100% schema description coverage, the schema already documents reminderId and even points to reminder_list as the source. The description adds no format or id-lookup detail beyond that, so baseline 3 is appropriate.

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 — 'Cancel a reminder so it never fires' — and immediately scopes it against the lead, conversation, and campaign steps. An agent can distinguish this from sibling deletions like lead_delete or message_delete 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?

Explicitly names the alternative for a related intent: 'To close a to-do instead use task_upsert with isCompleted.' This routes the agent between the two closest overlapping concepts (nudge vs. task) with a concrete parameter callout.

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