Delete an agent

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

The description adds 'permanently delete' and the confirm requirement, which is useful for a destructive operation with no annotations. However, it does not explain the dry-run behavior without confirm, environment defaulting, or other side effects; the schema partially covers the confirm semantics.

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?

One concise sentence with a command prefix, clear action, and key constraint. No filler or redundant content; it is easy to parse and front-loaded with the core purpose.

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 delete operation with fully documented parameters, the description plus schema covers the core invocation needs: what is deleted, permanence, the required bot parameter, and the confirm gate. It lacks usage alternatives and return/output context, so it is not fully complete, but it is sufficient for 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 schema already documents bot, confirm, and environment. The description repeats 'confirm: true' but adds no parameter meaning beyond what the schema provides, keeping it at the baseline.

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?

Description states a specific verb ('delete'), resource ('agent'), and scope ('from the environment'), with the qualifier 'permanently' clarifying the destructive action. This clearly distinguishes it from sibling tools like cs_quarantine_agent, cs_update_agent, or cs_delete_solution.

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?

No guidance on when to use this tool versus alternatives such as cs_quarantine_agent or cs_update_agent. The only directive is 'Requires confirm: true,' which is a prerequisite rather than a usage context or exclusion.

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