camofox_wait_for

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

No annotations present, so description must disclose behavior. It does not specify what happens if the selector is already present, error handling on timeout, return value, or relationship between selector and timeout (e.g., are both optional? exclusive?).

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 short but slightly redundant, stating 'Wait for a selector or timeout' followed by a similar sentence. Could be more concise by combining.

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 no output schema, no annotations, and 4 parameters with low schema coverage, the description fails to clarify return values, behavior when both selector and timeout are provided, or prerequisites. Important gaps remain.

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 only 25% (timeout described). The description adds 'CSS selector' for the selector parameter, but does not explain tabId, userId, or the format/syntax of selector. Minimal value beyond schema.

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 it waits for a CSS selector or timeout, specifying the resource (Camoufox tab) and the actions (wait, appear). It distinguishes from sibling tools that perform navigation or clicks.

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 implies usage when needing to wait for an element before further actions, but lacks explicit when-not or alternative tools. No exclusions or context for when to use versus other tools.

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