delete-glossary-term

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

With no annotations, the description carries the full burden but only states it deletes by UUID. It does not disclose the effect of optional parameters (hardDelete, recursive) or whether the operation is reversible, permissions required, or any side effects.

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 sentence, front-loaded with the key action and resource. It is efficient for a simple delete operation, though could expand on parameters.

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?

Missing critical context: no explanation of hardDelete and recursive parameters, no output schema, no error scenarios. For a mutation tool with optional destructive flags, the description is incomplete.

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 description coverage is 33% (only id described). The description adds no meaning beyond the schema; it does not explain 'hardDelete' or 'recursive', which are significant for behavior.

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 glossary term by UUID' clearly states the action (delete) and specific resource (glossary term) with an identifier (UUID). It distinguishes this tool from siblings like 'delete-glossary' and other delete-* tools.

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 guidance on when to use this tool versus alternatives such as 'update-glossary-term', 'create-glossary-term', or 'delete-glossary'. Lacks any context on prerequisites or scenarios.

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