delete_invoice_reminder

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

Annotations already indicate destructiveHint=true, readOnlyHint=false, and idempotentHint=true. The description adds no extra behavioral context, such as whether deletion is permanent, what happens to the associated invoice, or any side effects. It lacks information beyond what annotations provide.

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, short sentence with no wasted words. It is appropriately sized for a simple delete operation and front-loaded with the action.

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?

The description is minimal and does not explain the relationship between invoice_id and reminder_id, or any constraints or outcomes. With no output schema, the description does not mention return values or behavior when the reminder does not exist. Given the destructive nature, more context is expected.

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 coverage is 100%, with both 'invoice_id' and 'reminder_id' having descriptions in the input schema. The description adds no additional meaning or context about the parameters, so the baseline of 3 applies.

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 a delete action on a reminder resource. It is clear in meaning, but it does not specify that it is an invoice reminder, relying on the tool name to disambiguate. It does not explicitly differentiate from other delete tools, but the verb+resource is specific enough.

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 no guidance on when to use this tool vs. alternatives. There is no mention of prerequisites, conditions (e.g., only unsent reminders), or comparison to related tools like mark_as_sent_invoice_reminder or delete_invoice.

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