wait_ms

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

No annotations provided, but description fully discloses behavior: cap at 10000 ms, returns {'ok', 'action', 'requested_ms', 'waited_ms', 'clamped'}, explains 'clamped' flag meaning when cap exceeded. No contradictions.

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?

Two sentences: first defines purpose and cap, second explains return structure and alternative. No redundant words, information is front-loaded and efficient.

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 wait tool, description covers return values, behavior at cap, and alternative (settle_ms). No output schema visible but description provides details. Complete for its complexity.

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?

Only one parameter 'ms' (integer) with 0% schema description coverage. Description adds the cap constraint (10000 ms) but does not explicitly state the parameter represents milliseconds. The tool name 'wait_ms' implies milliseconds, but description could be clearer.

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?

Clearly states it's a 'wait' tool for page load or app draw. The verb 'wait' and resource implied (time) with specific use cases. Differentiates from siblings by mentioning 'settle_ms' as an alternative for observing results in the same call.

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?

Provides clear context: wait for page load or app draw, capped at 10000 ms. Suggests preferring 'settle_ms' on the action to observe the result simultaneously. Lacks explicit when-not-to-use but covers key usage guidance.

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