conversation_ai_delete_agent

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the destructive nature is known. However, the description adds no additional context, such as the irreversibility of the deletion, whether it permanently removes configurations, or any safety warnings. With no extra disclosure beyond the annotations, it fails to provide meaningful behavioral 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?

The description is technically concise, but it is under-specified rather than efficiently informative. Two words ('Delete Agent') add almost no value beyond the tool name and fail to earn their place. There is no structure or front-loading of critical information.

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 delete tool with one required parameter, the description is still inadequate. It does not clarify the scope of deletion (e.g., is it permanent? does it cascade to related resources?), nor does it mention any return values or success criteria. The agent has to infer behavior solely from the name and annotations, which is insufficient for safe and correct 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?

Schema coverage is 100%, so the parameter 'agentId' is fully documented with the description 'Conversations AI agent id'. The tool description adds nothing beyond the schema, but since the schema is already explicit, this meets the baseline for a single-parameter tool. No additional semantic value is required from the description.

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' states a verb and resource, but it is extremely generic. It does not specify that this is for Conversation AI agents, and there are sibling tools like agent_studio_delete_agent and voice_ai_delete_agent that delete different types of agents. Without context, an agent cannot clearly distinguish this tool from related ones.

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 usage guidance is provided. The description does not indicate when to use this tool versus alternatives such as conversation_ai_update_agent or agent_studio_delete_agent, nor does it mention any prerequisites or side effects. The agent is left with no basis for selection.

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