deleteAggregate

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

The description discloses that the action is destructive and irreversible ('Permanently delete', 'cannot be undone') and explains the host's approval gate. However, it does not mention potential side effects on related entities (e.g., invoices using the metric) or the return value.

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 three sentences, efficient and front-loaded. Each sentence adds value: purpose, destructiveness warning, and usage guideline. No extraneous information.

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 delete tool with no output schema and no annotations, the description provides essential information: what it does, when to call, and behavioral notes. It lacks details on error handling or edge cases, but is generally 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?

Schema coverage is 100%, and the description does not add meaningful parameter information beyond what the schema already provides. The aggregateId is described as UUID in the schema, and __userContext is internal. Baseline score of 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?

The description clearly states the tool's purpose: 'Permanently delete a Billable Metric.' It uses a specific verb ('delete') and resource ('Billable Metric'), and distinguishes from sibling delete tools by specifying 'THIS billable metric'. The purpose is 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?

Explicitly states when to use: 'ONLY call when the user explicitly says 'delete' or 'remove' for THIS billable metric.' Also instructs not to ask the user to re-confirm because the host enforces approval. This provides clear guidance on tool invocation.

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