read_website

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

The description adds valuable behavioral context beyond annotations: it mentions 'fast, token-efficient' performance and output format ('converts to clean Markdown while preserving links and structure'), which are not covered by annotations like readOnlyHint or idempotentHint. Annotations already indicate safe, non-destructive operations, so the description complements this without contradiction, though it could add more on rate limits or error handling.

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 front-loaded with key information ('Fast, token-efficient web content extraction') and uses two concise sentences that efficiently convey purpose, ideal use cases, and output format without any wasted words. Every sentence adds value, making it highly structured 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 the tool's moderate complexity (3 parameters, no output schema), the description is largely complete: it covers purpose, usage context, and behavioral traits. However, it lacks details on output specifics (e.g., what the Markdown output looks like or error cases), which would be helpful since there's no output schema. Annotations provide safety info, but more output context could enhance completeness.

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 description does not explicitly discuss parameters, but the input schema has 100% description coverage, providing full details on 'url', 'pages', and 'cookiesFile'. This high coverage means the schema carries the burden, so the baseline score of 3 is appropriate as the description adds no additional parameter semantics beyond what the schema already explains.

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's purpose with specific verbs ('extraction', 'reading', 'analyzing', 'gathering') and resources ('web content', 'websites'), and distinguishes its functionality by mentioning conversion to clean Markdown while preserving links and structure. It explicitly differentiates from potential alternatives by highlighting 'fast, token-efficient' extraction, making the purpose highly specific and actionable.

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 provides clear context on when to use this tool ('ideal for reading documentation, analyzing content, and gathering information from websites'), which helps guide usage. However, it does not explicitly state when not to use it or name alternatives, and with no sibling tools listed, there is no direct comparison. This results in strong but not exhaustive guidance.

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