chrome_wait_for

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

No annotations are provided, and the description mentions polling behavior but fails to disclose timeout limits, polling frequency, or whether the operation is read-only. The truncated description lacks critical behavioral details.

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 short and cut off mid-sentence, indicating poor structure and lack of completeness. It fails to convey necessary information efficiently.

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?

Given the absence of output schema and the truncated description, the tool's behavior upon condition fulfillment is unknown. The description does not adequately compensate for missing structured fields.

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 input schema has no properties, yet the description references a `text_match` parameter that is not defined in the schema. This inconsistency undermines clarity. With 0 parameters in schema, description adds no value and misleads.

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 indicates polling for a CSS selector or text match, but it is cut off, leaving ambiguity about the tool's exact output. However, the verb 'polls' and resource 'current Google Chrome tab' provide some clarity.

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 provides no guidance on when to use this tool versus alternatives like chrome_read_tab or chrome_query_selector_all. No contexts or exclusions are mentioned.

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