wait_for_firefox_tab

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

With no annotations, the description carries the normalization burden. It does disclose that it's event-driven and returns immediately if already loaded, which is valuable. However, it does not describe timeout behavior or what happens on failure. Thus, it's decent but not exhaustive.

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 sentences, the first states the core function immediately camiseta. Concise, front-loaded, no fluff.

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?

It's a simple tool with 2 params and no output schema. The description covers purpose, usage, and a key behavior (event-driven). It might benefit from explaining timeout behavior, but given simplicity, it's fairly 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?

Schema coverage is 50%: tabId has a description, timeoutMs does not. The description adds context for tabId (returned by open/duplicate) but doesn't explain timeoutMs beyond what's in the schema (type, default, range). With low coverage, the description should compensate more.

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 uses a specific verb+resource (

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 to use it after open/duplicate to know when page finishes loading. Could mention when not to use (e.g., for other browser tabs or polling), but the given scenario is clear.

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