Delete stored follow-up reminders

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

No annotations are provided, so the description bears full responsibility. It explains deletion, chain cancellation, bulk deletion, and optional Gmail label removal. However, it does not disclose irreversibility, error cases, or side effects beyond label removal.

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 a single paragraph with multiple sentences, packing considerable detail. It is relatively concise but could be improved with structural elements like bullet points for clarity.

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?

Given 12 parameters, no annotations, and no output schema, the description covers core functionality and usage modes. Missing details include return value, error scenarios, and prerequisites (e.g., account connection), but overall it is sufficient for an AI agent to use the tool correctly.

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%, so the description must explain parameters. It mentions most parameters (reminderIds, messageId, etc.) and explains their roles (e.g., cancelChain works with reminderIds). Although it groups them, it adds significant meaning beyond the schema's type-only definitions.

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 starts with 'Remove follow-up reminder(s) from the local store,' which clearly states the verb and resource. It distinguishes from siblings like followup_due, followup_send, and followup_trigger by focusing on deletion rather than triggering or sending.

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 provides concrete usage patterns: pass specific IDs, use cancelChain to drop chains, or use deleteAll with confirm. It implicitly guides when to use each parameter, but does not explicitly state when NOT to use or alternative tools.

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