paperclip_delete_agent

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

No annotations are provided, so the description must disclose behavior on its own. It only restates the action without mentioning permanence, side effects on associated resources, permissions, or that the operation cannot be undone. 'Terminate' hints at finality, but the description does not carry the full burden.

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 sentence with no filler and the action is front-loaded. It is well-sized for a one-parameter tool, though it mostly restates the tool name and adds little information.

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 one-parameter delete tool, the essential 'what' is present and the schema covers the parameter. However, with no annotations and no output schema, an explicit note about irrevocability or consequences would make it complete.

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 single parameter agentId is fully described in the input schema ('ID of the agent to delete'), so the description need not add much. It does not, but the 100% schema coverage keeps this at 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?

The description uses a specific verb ('Delete (terminate)') and a clear resource ('Paperclip AI agent'). It is unambiguously distinct from sibling agent tools like pause, wake, and update, and 'terminate' clarifies this is a kill operation rather than a state change.

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 is given about when to choose delete over pause or wake, nor any prerequisites such as the agent needing to exist or be stopped. The use case is only implied by the verb.

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