browser_documentation

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

No annotations are provided, but the tool is a read-only documentation lookup with zero parameters, so behavioral disclosure needs are minimal. The description accurately conveys it returns reference material and is non-destructive by nature, though it doesn't describe output size or format.

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, zero waste. The first sentence defines the deliverable precisely and the second provides actionable guidance. Every word earns its place, and it's appropriately front-loaded with the core purpose.

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?

For a zero-parameter documentation-retrieval tool with no output schema, the description is complete for its function. The only minor gap is not describing what the returned documentation contains structurally (code snippets, examples, etc.), but given the tool's simple nature, this is adequate.

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 tool has zero parameters with 100% schema coverage (there are no parameters to document). Per the rubric, 0 params = baseline 4. The description appropriately doesn't need to add parameter semantics since there are none to explain.

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 returns the full Chrome (browser use) API reference for the live browser/tab object graph. The verb 'Return' plus specific resource ('full Codex Chrome API reference') makes the purpose unambiguous, and it's clearly distinguished from siblings which are operational browser tools.

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 includes an explicit instruction to 'Read this before writing browser_exec code,' which establishes its role as a prerequisite for a sibling tool. It provides clear context for when to use it, though it doesn't enumerate exclusions or describe when NOT to use it relative to other documentation sources.

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