sleep

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

Description adds 'Blocks the calling process' and 'bounded by an upper safety limit' beyond the destructiveHint annotation. While annotations provide destructiveHint, the description clarifies the non-destructive nature of pausing, offering useful behavioral context.

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?

Three sentences, front-loaded with primary action, no superfluous words. Every sentence contributes meaning: action, preview ability, usage vs alternative.

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 full schema coverage and no output schema, the description covers purpose, usage, and behavioral hints adequately. It is complete enough for an agent to select and 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 description coverage is 100%, so the schema already documents all parameters. Description adds minimal value by mentioning 'bounded by an upper safety limit' and dry_run preview, but does not significantly enhance understanding 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?

The description clearly states 'Pause execution for a specified number of seconds' with a specific verb and resource. It distinguishes itself from sibling 'timeout' by explaining it is not for time-bounded command execution.

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 (use 'timeout' for deadlines). Also mentions --dry_run to preview behavior, providing clear guidance.

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