zen_wait_for_title

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It states the tool waits for a condition but omits details on polling frequency, timeout behavior (error vs. fallback), or return value. The mention of 'JS regex pattern' adds minimal context, but overall transparency is low.

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 a single sentence that directly conveys the core function. It is front-loaded and contains no extraneous words. However, its brevity sacrifices important parameter and behavioral details, which limits its completeness.

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 tool has 3 parameters, no output schema, and no annotations, the description is insufficient for an agent to use it correctly. It lacks explanation of parameters, return values, timeout effects, and tab identification. The description fails to provide a complete operational picture.

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 description coverage is 0% (no parameter descriptions in schema), and the tool description does not explain any of the three parameters (pattern, timeout, tab_id). It does not add meaning beyond what is evident from the schema structure. This severely impairs proper parameter usage.

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: wait for document.title to match a JS regex pattern. It specifies the verb (wait), the resource (document.title), and the condition (regex match). Among sibling tools with similar names (e.g., zen_wait_for_url, zen_wait_for_element), this description uniquely identifies its target.

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 explicit guidance on when to use this tool versus alternatives like zen_wait_for_url or zen_wait_for_element. It does not mention when not to use it or any prerequisites. The agent must infer usage solely from the purpose statement.

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