browser_read

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention network requests, side effects, session dependencies, or whether reading modifies the page state. The terse phrase 'Read page content or fetch URL' gives no insight into operational behavior.

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 extremely concise (single sentence), with no wasted words, which is good for readability. However, it is under-specified—it conveys almost no actionable detail, so the conciseness is not effective in communicating how to call the tool correctly.

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 a complex ecosystem of sibling tools and no output schema, the description is incomplete. It does not explain return formats, default behavior (active tab handling), or the role of filter and session parameters in practice. An agent would struggle to use this correctly without inspecting the schema and other tools.

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 100%, so each parameter (url, filter, session) already has a clear description. The tool description does not add any extra meaning about how the parameters interact, such as the active-tab default when url is omitted, but per the baseline rule for high coverage, a 3 is appropriate.

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 states a verb ('Read') and a resource ('page content') but 'fetch URL' is vague and ambiguous. It does not specify what the tool returns or how it differs from siblings like browser_get, browser_navigate, or browser_snapshot. It is more specific than a pure tautology but lacks functional specificity.

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 is given on when to use this tool versus alternatives. With 30+ sibling tools, the description does not mention any conditions, exclusions, or when to prefer browser_navigate for navigation or browser_snapshot for visual captures. The agent must infer usage from the name and schema.

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