delete_reminder

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

The description discloses an important behavioral safeguard (the confirm=true requirement), but with no annotations, it does not cover other behavioral aspects such as irreversibility, side effects, or error conditions. The deletion itself is implied by the tool name, but the description adds limited transparency beyond the confirmation gate.

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: first states the purpose, second adds the essential confirmation instruction. No redundant words, perfectly front-loaded and easy to parse.

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 simple delete tool, the description covers the core action and the key prerequisite, and the output schema exists for return values. However, it lacks any mention of irreversibility, permissions, or failure scenarios, which are relevant for a destructive operation. It is minimally adequate but not complete.

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 0% schema description coverage, the description compensates by explaining the confirm parameter ('pass confirm=true'), which is critical. However, reminder_id is not elaborated beyond its name, and no format or source is specified. The added meaning for confirm is valuable but incomplete overall.

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 'Delete a reminder' clearly states the action (delete) and the resource (reminder), distinguishing it from sibling tools like update_reminder or list_reminders. It is concise and unambiguous.

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 explicit usage context: 'caller must pass confirm=true after user approval.' This is a clear prerequisite. However, it doesn't enumerate alternatives or situations when to avoid using this tool, though the match with siblings is obvious.

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