delete-glossary-term

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

With no annotations, the description must disclose behavioral traits but only states 'Delete a glossary term by UUID'. It fails to explain the meaning and effects of the optional parameters 'hardDelete' and 'recursive', nor does it mention if the deletion is permanent or reversible.

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 single sentence is concise but sacrifices completeness by omitting crucial parameter details and behavioral context. While front-loaded, it is too minimal for the tool's complexity.

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 mutation tool with three parameters and no output schema, the description lacks explanation of return values, error conditions, default parameter behavior, and side effects. It is incomplete and insufficient for correct agent 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?

The schema has 33% description coverage (only 'id' has a description). The tool description adds no semantic information beyond the schema. The meanings of 'hardDelete' and 'recursive' remain undocumented in both schema and description, creating ambiguity.

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 uses a specific verb ('Delete') and resource ('glossary term') with the identifier method ('by UUID'), making its purpose distinct from sibling tools like 'delete-glossary' (deletes entire glossary) and 'update-glossary-term' (update vs delete). It is not a tautology and effectively differentiates.

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 provides no guidance on when to use this tool versus alternatives such as 'delete-glossary' or 'update-glossary-term'. No context about prerequisites, exclusions, or appropriate scenarios is given.

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