browser_read_page

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

Describes stripping non-content and token efficiency, but with no annotations, missing details like error handling, auth requirements, or whether links/images are preserved. Adequate 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?

Very concise: three sentences plus bullet arguments. No wasted words, front-loaded with purpose. Efficiently communicates key information.

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 two simple parameters and an output schema, description covers purpose, usage, and parameter semantics. Lacks a bit on behavioral edge cases but overall sufficient.

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?

Adds meaning beyond schema by explaining page_id and max_length with defaults. Schema had only titles, so description adds value, though could include more detail like format of page_id.

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 it returns page content as clean, readable markdown, stripping navigation/ads. Differentiates from sibling tools like screenshot or snapshot by focusing on textual content.

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?

Indicates 'Best for reading articles, docs, search results' providing clear usage context. Does not explicitly state when not to use or name alternative sibling tools, but context is sufficient.

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