desktop_wait

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

With no annotations, the description carries the burden of explaining behavior. It states the core behavior (sleep for the given seconds) and implies no other side effects. It does not mention return value or absence of state changes, but for a wait operation this is implicit and sufficient.

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?

The description is extremely concise: two short sentences with no filler. It states the action and the key usage caution, making every word valuable.

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, the description is complete enough: it explains the operation and gives a usage preference. There is no output schema needed for a side-effect-free sleep. It could mention why waiting is sometimes necessary, but the current context is adequate.

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 already provides the parameter name, type, minimum, and maximum. The description only repeats 'seconds' in the phrase 'Sleep for `seconds` seconds' without adding further semantic detail beyond what the schema supplies, so it stays at the baseline.

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 the tool's purpose: to sleep for a specified number of seconds. The verb 'Sleep' and the parameter 'seconds' make the action and resource unambiguous.

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 description gives explicit usage guidance: 'Use sparingly' and 'prefer screenshot-then-act', which directs the agent toward a preferred alternative. It does not go into detail about exactly when waiting is appropriate, but the guidance is clear enough for this simple tool.

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