wait

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

No annotations are provided, so the description carries the behavioral burden. It discloses the 60-second cap and the reason waits are needed, but omits whether the call blocks, what default duration applies when seconds is omitted, and what happens above 60 seconds.

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 sentence, front-loaded with the action and cap, and the parenthetical rationale earns its place by explaining why the tool exists.

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 one-parameter sleep tool, the description covers purpose and cap but leaves default behavior and sibling routing unspecified. Without annotations or an output schema, those omissions are noticeable.

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 0%, so the description must explain the sole parameter. It implies the parameter is a duration in seconds capped at 60, but does not state whether it is optional, what default applies if omitted, or how values over 60 are handled, so compensation is only partial.

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?

States a specific action ('Sleep') and scope ('up to 60 s'), with a rationale ('guest is slow; animations take time'). It does not distinguish this fixed sleep from siblings like wait_for or settle, so it is not a 5.

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 parenthetical gives a use case (waiting for slow guest animations) but does not explicitly say when to choose this over wait_for/settle or when not to use it. Guidance is implied rather than stated.

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