fetch

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

With no annotations provided, the description carries the full burden and does well: it discloses output format, query-based passage filtering, PDF page labels, and that JavaScript-heavy pages load via headless Chrome with slower performance. It omits error behavior, auth requirements, and rate limits, but provides substantial behavioral context beyond the schema.

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 three tightly written sentences that front-load the core action and then add useful behavioral details. Every sentence contributes context about output, filtering, or performance, with no wasted wording.

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?

For a tool with no annotations and no output schema, the description is mostly complete: it covers output format, query filtering, PDF handling, and JavaScript rendering behavior. It could go further on failure modes or multi-URL aggregation, but it is adequate for correct invocation.

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%, so the baseline is 3. The description adds meaningful semantics for `query` and its interaction with `max_tokens`, clarifying that only relevant passages are returned within the token budget, and notes PDF page labeling.

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 specific verb ('Read') and resource ('web pages or PDFs') and clearly names the output format ('clean markdown'). It does not explicitly differentiate itself from sibling tools like 'crawl' or 'links', so sibling distinction is left implicit.

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?

Usage is implied by the description: use this to read specific pages or PDFs, optionally with `query` to extract relevant passages. However, there is no explicit guidance on when to use this instead of alternatives like `crawl` or `links`, which is a clear gap.

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