sleep

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

Description discloses blocking behavior and safety cap, but contradicts annotations: annotations mark destructiveHint=true, yet sleep is not destructive (no state modification). This inconsistency misleads the agent.

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, front-loaded purpose, no fluff. Every sentence adds value.

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 no output schema and full parameter schema, the description provides sufficient context about use cases, distinctions, and safety limits.

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 all 3 parameters fully (100% coverage), so description adds no extra meaning beyond what parameter descriptions provide. Baseline 3 is appropriate.

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 what the tool does: 'Pause execution for a specified number of seconds' with a safety cap. It distinguishes from the sibling 'timeout' by saying 'Not for time-bounded command execution — use 'timeout'.

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?

Explicitly states when to use ('introduce delays between operations') and when not to use (time-bounded execution, use 'timeout' instead). Also mentions --dry_run for previewing duration.

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