wait

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

The annotations already declare this as a safe, idempotent, non-open-world read (readOnlyHint=true, idempotentHint=true, destructiveHint=false), so the safety profile is covered. The description adds that it blocks for a 'short duration' and is a compatibility alias, but does not disclose that it pauses execution or what the alias replaces.

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 tight sentence with the alias status front-loaded. No waste, though it is arguably too terse to route the agent correctly.

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, zero-required, fully annotated tool this is minimally adequate, but 'compatibility alias' is left unexplained (alias for what, and should it be avoided?), which is a real gap for correct tool selection.

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 coverage is 100% and the single 'duration' parameter is fully documented in the schema with its default. The description's 'short duration' phrase adds only mild corroboration and no syntax or unit detail beyond the schema's 'Seconds to wait. Defaults to 1.'

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 states a verb (wait) and a scope (a short duration), and the 'compatibility alias' label hints at its legacy status, but it does not differentiate itself from the more specific siblings wait_for_window and wait_for_close, which an agent could easily confuse it with.

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?

There is no explicit when-to-use or when-not-to-use guidance. 'Compatibility alias' implies a preferred modern alternative exists but never names it, leaving the agent to guess whether to use this or a sibling.

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