delete_agent

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

With no annotations provided, the description carries the full behavioral disclosure burden. It explicitly states the operation is permanent, which is critical for a destructive action. It does not detail cascading effects on associated calls or authentication requirements, but the core irreversibility is clearly communicated.

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, front-loaded sentence with zero filler. Every word contributes meaning, and the destructive, irreversible nature is communicated immediately.

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 one-parameter delete tool, the description plus schema is adequately complete. It identifies the action, the target, the required input, and the permanence of the operation. Additional caveats about side effects or error handling would be useful but are not essential for basic 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 description coverage is 100%, so the sole parameter 'id' is already well documented as 'Agent ID to delete'. The description adds no additional parameter-level context, but this is acceptable given the schema fully covers it.

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 states a specific verb ('permanently delete') and a concrete resource ('voice AI agent'), clearly distinguishing it from list_agents, get_agent, create_agent, and update_agent. The word 'permanently' adds important scope beyond the tool name.

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 purpose is clear enough that an agent can infer it is for removing an agent rather than reading or modifying it. However, there is no explicit guidance about when not to use it, prerequisites, or alternatives such as update_agent for reversible changes.

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