task_resume

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

The description discloses selection logic for when no name is provided (most recent active, then most recent paused). With no annotations provided, this adds valuable context beyond the tool's name, though it does not mention potential errors or side effects.

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 concise yet informative, front-loading the core purpose and including usage triggers and fallback logic in a compact format.

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 tool with one optional parameter and an output schema, the description covers the essential aspects: purpose, usage, parameter semantics, and default behavior. It does not mention error handling, but that is likely covered by the output schema or is unnecessary.

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 description explains the 'name' parameter as an optional task name or ID, and clarifies the default behavior when omitted. Given the schema has no descriptions, this fully compensates for the 0% schema coverage.

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 'Continue a task, reactivating it when paused' with a specific verb and resource. It distinguishes from sibling tools like task_load by emphasizing reactivation and fallback behavior.

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?

It explicitly specifies trigger phrases including natural language examples and 'resume'. It describes the fallback behavior without naming alternatives, so it lacks explicit when-not-to-use guidance but provides clear context.

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