iyke_wait

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

No annotations exist, so description carries full burden. It discloses the return format ({ satisfied, elapsed_ms, message? }) and implies synchronous, non-destructive waiting. Could add that it blocks until condition or timeout.

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 concise sentences, front-loaded with purpose, no redundancy. Every sentence adds value.

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?

While the usage guidance and return shape are helpful, the lack of parameter explanations for the predicate types and timeout makes it incomplete for reliable tool invocation without additional schema descriptions.

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 0%, but description only mentions 'predicate' without explaining the four parameters (kind, value, pane, timeout_ms). The enum values for kind (text, selector, etc.) are left undefined, limiting agent understanding.

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 'Wait until a predicate is satisfied or timeout,' defining the tool's verb and resource. It distinguishes itself from siblings by advising use after iyke_click/iyke_go instead of fixed sleeps.

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?

Explicitly says when to use ('after iyke_click/iyke_go to wait for new state to render') and provides an alternative context ('instead of fixed sleeps'), giving clear usage guidance.

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