Delete agent

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

The description reinforces the destructive hint with 'permanently deletes' and 'cannot be undone', and adds that it returns a confirmation. It does not contradict the idempotent hint, though it does not explain idempotency behavior.

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 concise sentences that front-load the key information. Every word adds value, no filler.

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 deletion tool with one parameter and no output schema, the description is sufficiently complete. It could specify the format of the confirmation, but the current text is adequate.

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 already has 100% coverage with a description for agent_uuid. The description adds 'by its uuid', which is redundant. No additional parameter meaning is provided beyond the schema.

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 clearly states the action (permanently deletes), resource (agent), and method (by uuid). It distinguishes well from sibling tools like evaluate_agent or list_recent_runs, none of which involve deletion.

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 implies when to use (when you want to permanently delete an agent) and notes the irreversible nature, but does not explicitly state when not to use or list alternatives. However, given the unique deletion purpose among siblings, this is clear enough.

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