delete_recurring_invoice

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

No annotations are provided, so the description carries the full burden. It only states 'Delete' without disclosing permanence, cascading effects on scheduled invoices, or any authorization requirements. For a destructive operation, this is significantly underspecified.

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?

One concise sentence with the action verb front-loaded and no unnecessary words. Every word earns its place.

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 one-parameter delete tool, the core purpose is clear, but the lack of behavioral context (irreversibility, impact on related invoices) and absence of any output schema make it minimally complete but not richer.

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?

The input schema provides 100% coverage with id described as 'The recurring invoice UUID', so the description adds no parameter information. The baseline of 3 applies because the schema already documents the only parameter adequately.

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 recurring invoice template' uses a specific verb ('Delete') and a precise resource ('recurring invoice template'), clearly distinguishing it from siblings such as delete_invoice (regular invoices) and pause_recurring_invoice (temporary suspension).

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?

No explicit when-to-use or alternatives are provided. The tool's name and description imply it is for deleting recurring invoice templates, but there is no guidance on when to choose this over pausing or deleting issued invoices, or on prerequisites like the template not being in use.

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