delete_agent

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

Discloses key traits: soft-delete, agent becomes inactive, unarchiving not supported. Despite no annotations, reveals constraints and irreversible nature. Lacks mention of permissions or side effects, but sufficient for this simple tool.

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?

Three concise, front-loaded sentences. Every sentence adds value: action, constraint, limitation and alternative. No unnecessary words.

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?

Given no output schema and simple single-parameter tool, description provides all necessary context: what it does, constraints, and alternative for restoration. Agent can correctly decide when to invoke.

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 covers parameter fully (100% coverage), description simply restates agent ID context. Description adds no new semantic meaning beyond the schema, meeting baseline expectation.

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?

Clearly states the action (archive/soft-delete), the resource (agent by ID), and the effect (inactive). Distinguishes from sibling tools like delete_audience and delete_campaign by focusing on 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?

Explicitly mentions when to use (to archive an agent), when not to use (cannot archive agents with active campaigns), and alternative for restoration (use app.smallest.ai). No ambiguity.

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