Api terminologies destroy

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered by structured data. The description contributes nothing beyond that—no disclosure of what a terminology is, what dependent data is removed, or whether deletion is recoverable.

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 restated identifier, which is under-specification rather than conciseness. There is no front-loaded purpose statement to earn the (admittedly small) space.

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 destructive tool with a required id and no output schema, the description is inadequate—nothing about what is being deleted or the consequences. Annotations cover the destructive flag, but the semantic context an agent needs to choose this tool is absent.

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 single required parameter `id` has 0% schema description coverage, and the description does not explain what the id refers to or its format. With no compensating text, the agent gets no meaning beyond the bare string type.

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 is only the string "api_terminologies_destroy", which restates the tool name verbatim. The name does imply a delete operation on terminologies, but the description adds no verb+resource explanation, no scope, and no differentiation from the many sibling destroy endpoints.

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?

There is no guidance on when to use this tool, when not to, or what alternatives exist. An agent must infer from the name alone that this deletes a terminology record.

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