safari_read_page

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

No annotations provided; description carries full burden. It discloses return values (title, URL, body text) and parameter effects but does not cover error handling, prerequisites, or non-destructive nature explicitly. Basic read-only intent is clear but could be more comprehensive.

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?

Three sentences, no fluff. Purpose stated first, then usage guidance, then parameter explanations. Efficient and easy to parse.

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 no output schema, description explains return content (title, URL, body text) and parameter limits. Missing edge cases or error states, but adequate for a simple read tool.

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 100% with descriptions; description adds value by clarifying usage: 'Use selector to read specific element. Use maxLength to limit output.' This goes beyond schema alone.

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 explicitly states the tool reads page text content (title, URL, body text) and is for reading articles or page content. It distinguishes from sibling safari_snapshot which provides reference IDs for interaction.

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?

Clear guidance: 'For interacting with elements, prefer safari_snapshot (gives ref IDs).' This tells when to use this tool vs. an alternative, plus explains parameters selector and maxLength.

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