Delete Unit Of Measure

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

The description explicitly states 'This cannot be undone' and 'permanently removes', reinforcing the destructiveHint=true annotation. It adds behavioral context beyond the annotation by emphasizing irreversibility. No contradictions 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 is relatively short and front-loaded with the purpose. However, it redundantly repeats 'This cannot be undone' and includes API endpoint details that, while informative, are not essential for an agent's selection. Could be slightly more concise.

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 complete schema and annotations, the description adequately covers the essential behavior. It mentions permanence and required parameters. Lacks discussion of idempotency (hinted by annotation) or error handling, but overall sufficient for correct invocation.

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%, so the schema already documents the parameters. The description only repeats the required parameter names without adding further semantics like format constraints or examples, meeting the baseline.

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 action ('Delete a Unit of Measure (UOM)'), specifies the resource type, and implies the scope by naming the endpoint. It distinguishes itself from sibling tools like 'create_unit_of_measure' or 'update_unit_of_measure' by focusing on deletion.

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 tells when to use the tool ('to permanently delete'), but provides no guidance on when not to use it, alternatives, or prerequisites. It lacks context about preconditions (e.g., if the UOM must exist) or comparisons to other actions like deactivation.

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