wait

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

With no annotations, the description carries full behavioral disclosure. It clearly indicates the tool blocks/pauses execution for the provided duration and that the only effect is a time delay. This is accurate, though it omits details like valid range or potential timeouts.

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?

A single, front-loaded sentence that conveys the action, the unit, and the sequencing. No filler or repetition.

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 one-parameter sleep tool with no output schema, the description is nearly complete. It could add a brief note about return behavior or accepted ranges, but these are minor for an agent deciding to invoke it.

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 schema provides only a type for 'duration' with no description, so the description's clarification that the value is in milliseconds is valuable. It gives the agent the essential semantic needed to call the tool correctly.

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 uses an explicit verb ('Wait') with a specific resource/duration and states the unit. It is unambiguous and distinct from all listed siblings, none of which perform a delay.

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?

The phrase 'before proceeding' implies the tool is used as a pacing step, but the description does not explicitly state when to prefer it or mention any alternative/condition. This is adequate but leaves the when-to-use guidance to inference.

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