wait_until

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

Discloses blocking limit of ~1.5s, reason for limit, and return behavior ('not yet'). Exceeds annotation information without contradiction.

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?

Three sentences, front-loaded purpose, no unnecessary words, highly concise.

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?

Covers return behavior and constraints well, but missing explanation of timeout_ms parameter. For a simple polling tool, nearly complete.

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?

Conditions are described with a list of valid values, adding meaning to the condition parameter. However, the timeout_ms parameter is not explained at all, despite 0% schema coverage.

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 waits for a condition and lists valid conditions. However, does not explicitly differentiate from sibling tools like wait_for_node or get_play_state, making it clear but not distinct.

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 on blocking behavior and calling again if condition not met. Does not explicitly compare to alternatives, but the guidance on how to use is sufficient.

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