delete_agent

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states irreversibility, the impact on assigned phone numbers, that active calls continue, and that new calls become impossible. This is rich behavioral context that goes far beyond what the schema provides.

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 three sentences long and front-loaded with the core action. Every sentence adds essential information: irreversibility, side effects, and a safer alternative. There is no wasted wording.

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?

The tool is simple (one parameter) and the description covers the critical behavioral aspects, the alternative, and the irreversible nature. An output schema exists, so return-value details are not needed. The description is fully adequate for an agent to invoke this tool correctly.

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 schema has one parameter (agent_id) with zero description coverage. The tool description does not mention the parameter at all, failing to compensate for the lack of schema documentation. Although the parameter name is self-explanatory, the description should explicitly confirm what agent_id refers to, especially when schema coverage is 0%.

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 opens with 'Permanently delete a voice AI agent,' which is a specific verb and resource. It clearly distinguishes the tool from siblings like update_agent, which can disable rather than destroy, and from read-only tools like get_agent or list_agents.

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 explicitly recommends an alternative ('consider using update_agent with is_active=False to disable the agent without destroying its configuration') and provides clear context for when permanent deletion is appropriate. This gives the agent actionable guidance on tool selection.

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