delete_glossary_term

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

The description discloses the destructive and irreversible nature, aligning with the destructiveHint=true annotation. It also mentions the return value '{deleted}'. However, it does not address idempotency (idempotentHint=true), which would clarify that multiple identical calls produce the same result. 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?

Three concise sentences. The purpose is stated first, followed by key behavioral warnings and return value. No unnecessary words or redundancy.

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 one-parameter tool with annotations and no output schema, the description adequately covers the action, parameter source, side effects, and return value. It is complete and leaves no ambiguity about usage.

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 parameter 'term_id' is already fully described in the schema with the same guidance ('from list_glossary'). The description reinforces this by mentioning lookup. Given 100% schema coverage, the description adds marginal value but is still helpful for emphasizing the source of IDs.

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 'Delete one business glossary term by its id', specifying the verb and resource. It distinguishes itself from sibling tools like add_glossary_term and list_glossary by explicitly mentioning deletion and id lookup.

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 advises to 'Look up ids with list_glossary', providing clear context for obtaining the required parameter. It also warns 'Destructive and not reversible', indicating when to use caution. However, it does not explicitly state when not to use this tool or list alternatives.

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