browser_read_page

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'Read the content and metadata', which implies a non-destructive read, but does not explain if the page needs to be loaded first, what exactly constitutes content and metadata, or if any side effects occur. This is insufficient for safe invocation.

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?

Single sentence, front-loaded and direct. No filler or redundancy. Every word is necessary.

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 zero parameters, no output schema, and many sibling tools, the description is too minimal. It does not clarify the output format (e.g., raw HTML, markdown, structured JSON) or behavior (e.g., does it wait for full page load?). The reference to browser_docs is insufficiently self-contained.

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?

Input schema has zero parameters, so schema description coverage is 100% (trivially). The description adds no parameter info, but there is nothing to add. Baseline for 0 parameters is 4.

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?

Description clearly states the tool reads content and metadata of the current page. The verb 'Read' and resource 'current page' are specific, and it distinguishes from many sibling tools that perform actions or retrieve other data. However, it does not explicitly differentiate from similar read tools like browser_get_text or browser_get_dom.

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?

No guidance on when to use this tool versus siblings. The description is just a statement of function, with no context for selection or exclusions. The reference to 'see browser_docs' is vague and not helpful for immediate decision-making.

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