voice_ai_delete_agent

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the baseline for adding context is lower. However, the description adds zero behavioral information beyond the annotations—it does not mention permanence, side effects, cascading deletions, or any operational details. It simply restates the action, providing no additional transparency.

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?

While the description is extremely concise (two words), it is under-specified rather than efficiently written. It lacks any structure or additional context, offering no information that would help an agent. Conciseness is not a virtue when it omits necessary details.

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 operation with no output schema, the description should at least indicate the effect (e.g., permanent deletion) or any required preconditions. The current description is inadequate—it tells an agent nothing about what deletion entails or what to expect. Even with the annotations, the description fails to fill the gaps.

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 100%, and both parameters (agentId, locationId) have descriptions in the schema. The description adds no information beyond what the schema already provides. With full schema coverage, the baseline of 3 is appropriate; the description does not enhance parameter understanding (e.g., how to find the agentId).

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 Agent' is essentially a restatement of the tool name 'voice_ai_delete_agent' and provides no additional specificity. It does not distinguish this tool from siblings like agent_studio_delete_agent or conversation_ai_delete_agent, even though they operate on different agent types. The verb and resource are present but the description is tautological.

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 versus alternatives. Multiple sibling delete tools exist (agent_studio_delete_agent, conversation_ai_delete_agent, voice_ai_delete_action), but the description offers no context for selecting among them. No prerequisites, exclusions, or scenarios are mentioned.

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