s_fetch_page

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key behaviors: bot-detection avoidance, performance characteristics of modes, pagination support, output format structure ('METADATA: {json}\n\n[content]'), and truncation handling. It doesn't mention rate limits, authentication needs, or error conditions, but covers most essential operational aspects.

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 well-structured and appropriately sized. It starts with the core purpose, adds usage guidelines, describes output format, then details parameters in a clear 'Args:' section. Every sentence adds value, though the parameter explanations could be slightly more concise.

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 5 parameters with 0% schema coverage and no annotations, the description does an excellent job covering the tool's functionality. It explains purpose, usage, behavior, parameters, and output structure. The presence of an output schema means return values don't need explanation. The main gap is lack of error handling or edge case information.

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 0%, so the description must compensate. It provides meaningful context for all 5 parameters: explains what 'url' is for, defines 'mode' options and their purpose, specifies 'format' choices, clarifies 'max_length' as character limit, and describes 'start_index' for handling truncation. This adds substantial value beyond the bare schema, though some details like default values are only in the schema.

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: 'Fetches a complete web page with pagination support. Retrieves content from websites with bot-detection avoidance.' This specifies the verb ('fetches'), resource ('web page'), and key capabilities ('pagination support', 'bot-detection avoidance'). It doesn't explicitly differentiate from sibling tool 's_fetch_pattern', but the purpose is well-defined.

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 explicit guidance on when to use different modes: 'For best performance, start with 'basic' mode (fastest), then only escalate to 'stealth' or 'max-stealth' modes if basic mode fails.' This gives clear operational advice and distinguishes between modes based on performance and fallback scenarios.

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