Auth Fetch

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

Describes the process: opens browser, user logs in, clicks capture, returns cleaned HTML. Mentions media preservation. No annotations, so description carries full burden. Minor omission of error handling, but generally transparent.

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?

Four sentences, front-loaded with purpose, each sentence adds value. No redundancy, precise language.

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?

No annotations or output schema, but description explains return type (cleaned HTML) and links to sibling tool for downloads. Lacks error handling details but adequate for a user-interaction 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?

Both parameters are documented in schema (100% coverage). Description adds no extra semantic information beyond schema. Baseline 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 clearly states it fetches web page content using a real browser and returns cleaned HTML. It distinguishes from general fetch tools by specifying use case for login-required pages, with concrete examples.

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?

Explicitly states MUST be used instead of Fetch/web_fetch for pages requiring login or returning empty HTML. Also instructs not to suggest copy-paste or PDF export. Provides clear when-to-use guidance.

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