paperclip_resume_agent

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

Discloses return type (updated agent object with status set to active), error handling codes (401, 404, 422) with corrective actions, and prerequisite state (agent must be paused). No contradictions with annotations (idempotentHint is reasonable).

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?

Concise yet comprehensive with clear sections (Args, Returns, Examples, Error Handling). Every sentence adds value; no redundancy.

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?

Complete for a simple tool: covers input, output, usage guidance, and error scenarios. No output schema needed as return is described.

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 param fully (100% coverage). Description adds an example value ('agt_abc123') and links param to error conditions, providing helpful context beyond 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?

Description clearly states the tool resumes a paused agent, using specific verb and resource. It effectively distinguishes from sibling tools like pause_agent or terminate_agent.

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?

Provides explicit use cases ('re-enabling an agent after pausing it for maintenance or incident response') and when not to use ('if the agent is not paused'), with guidance to check status first using another tool.

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