paperclip_terminate_agent

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

Description adds irreversibility, return value details, and authentication requirements (board API key) beyond the destructiveHint annotation. No contradictions observed.

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?

Every sentence contributes value. Organized into clear sections (Args, Returns, Examples, Error Handling) with a warning emoji for emphasis. No fluff.

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 a single required parameter, no output schema, the description fully covers return value, error scenarios, and usage constraints. It's complete for an agent to invoke correctly.

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 has 100% coverage with description for agentId. Description adds an example value ('agt_abc123') and confirms it's a UUID, providing extra context 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 tool 'permanently deactivate an agent' with an irreversible action. It distinguishes from siblings like paperclip_pause_agent by emphasizing permanence.

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?

Explicit 'Use when' and 'Don't use when' sections provide clear context, directing the agent to paperclip_pause_agent for temporary stops. Error handling codes are also detailed.

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