delete_agent

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action is a delete, but does not mention whether deletion is permanent, whether it cascades to associated tools/skills, or whether any confirmation or permissions are required.

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 short sentence that front-loads the primary action and target. Every word earns its place; there is no redundancy or superfluous detail.

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 delete operation, the description is minimally adequate but lacks mention of return behavior, destructive consequences, or effect on related resources. It is complete enough for a very simple tool but not richly informative given no annotations or output schema.

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 documents agent_id as a required string with 0% description coverage. The description only repeats 'by ID', adding minimal meaning beyond the schema and no additional format, source, or lifecycle context.

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 'Delete an agent by ID' uses a specific verb and resource, clearly distinguishing it from sibling tools like delete_skill or delete_flow. It unambiguously states the operation and target.

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 phrase 'by ID' implies an agent ID is needed and that the tool is appropriate when deleting a specific agent. However, it provides no explicit guidance about prerequisites, irreversibility, or when to prefer alternatives like update_agent.

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