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

With no annotations, the description carries the behavioral disclosure burden. It explicitly states 'Permanently delete' and 'NOT reversible,' which are critical behavioral facts. It also adds the approval prerequisite. It does not describe cascading effects or permissions, but for a single-resource delete this is adequately transparent.

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?

Two short sentences deliver the core action, irreversibility, and the required approval step. No filler or repetition; the most important safety information is front-loaded.

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 one-parameter destructive operation with no output schema, the description covers the essential context: what is deleted, that it is irreversible, and the prerequisite preview/approval flow. It could mention what happens to related data or the return response, but those are minor given the tool's simplicity.

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 0%, and the description does not explicitly document the `id` parameter. However, with only one required `id` property and a tool named delete_agent, the parameter's meaning is reasonably inferable. The description adds no format, source, or validation detail, so it only partially compensates for the missing schema documentation.

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 uses a specific verb and resource: 'Permanently delete an agent.' It also distinguishes the tool from its preview sibling by naming `preview_delete_agent`, and the resource differs clearly from delete_campaign and other deletion tools.

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 gives an explicit invocation condition: only call after the user has reviewed `preview_delete_agent` output and explicitly approved. This is a clear when-to-use gate and helps the agent avoid destructive action without confirmation.

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