voice_ai_delete_action

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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the description does not need to restate that this is a mutation. However, it adds no new behavioral context—such as whether the deletion is permanent, irreversible, or cascades to associated data. The description is purely redundant with the tool name and annotations, providing no extra transparency beyond what is already structured.

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 extremely concise—only four words. While it is front-loaded and free of fluff, it is also under-specified, offering no explanatory value beyond the tool name. It is not verbose, but it does not earn points for good structure because it is merely a repetition of the title.

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, the description is incomplete. It lacks any mention of what happens to the action, whether deletion is permanent, or what response to expect (since there is no output schema). Given the tool has three parameters and potential side effects, an agent would benefit from knowing that this is irreversible and possibly warn before calling. The description provides no such context.

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 input schema covers 100% of parameters with clear descriptions (agentId, actionId, locationId including its default). The description adds no additional meaning or syntax details. With full schema coverage, the baseline of 3 is appropriate; the description does not compensate for any gaps because there are none.

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 Action' clearly states a specific verb (delete), a resource (Agent Action), and distinguishes this from sibling tools like voice_ai_update_action and voice_ai_get_action. An agent can immediately understand the tool's function without ambiguity.

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 is provided on when to use this tool, when not to, or what conditions apply. It does not mention alternatives or any prerequisites (e.g., that deleting an action might affect active agents). The description offers no context beyond the operation itself.

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