Delete Tax Type

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

Annotations already indicate destructiveHint=true and idempotentHint=true. The description reinforces 'This cannot be undone' and 'permanently removes', which aligns with annotations but adds minimal additional behavioral context (e.g., no mention of authorization, side effects, or response behavior). No contradiction with annotations.

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 contains redundancy with repeated phrases ('This cannot be undone', 'Permanently removes the specified Tax records') and includes extraneous API details that could be trimmed. The core message is front-loaded but overall efficiency is mediocre.

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 with no output schema and two well-documented params, the description covers the core action and confirms permanence. However, it lacks guidance on prerequisites, error conditions, or post-deletion state, making it 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?

The input schema has 100% description coverage, so baseline is 3. The description mentions 'Required parameters: id, company_id' but adds no extra meaning beyond the schema's field descriptions, which already specify each parameter's role (URL path vs query string).

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 action (delete) and resource (Tax Type), with the verb+resource pattern. It explains that it permanently deletes Tax records. However, it does not differentiate from similar siblings like 'delete_tax_code' beyond the resource name, missing an opportunity to clarify unique scope.

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 says 'Use this to permanently delete' but provides no guidance on when to use this tool vs alternatives, such as whether there are other ways to remove tax types or when not to use it. It lacks exclusion criteria or alternative suggestions, leaving the agent to infer context.

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