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

The description discloses that it only accepts public URLs and returns clean Markdown, which aligns with the readOnlyHint annotation. It also explicitly states that private/internal hosts are blocked, providing behavioral constraints beyond the annotations.

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 concise, using two sentences to convey the core functionality, use case, and a key limitation. No redundant or extraneous information is present, making it 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?

While there is no output schema, the description clearly states the return format (clean Markdown). It also notes the URL limit (up to 10) and the restriction on private/internal hosts. It lacks details on error handling or response structure, but for a tool with a single input array, this is largely sufficient.

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 single parameter 'urls' is described as 'public URLs' and the schema already specifies 'http/https URLs' with a minimum and maximum. The description adds clarity by reinforcing the 'public' aspect and the output format (clean Markdown), but does not introduce additional parameter details beyond 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?

Clearly states it fetches up to 10 public URLs and returns clean Markdown in one call, explicitly distinguishing itself from single-page tools like scrape_page and read_url. The mention of 'research/RAG over several pages at once' further clarifies its intended use case.

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?

Provides implicit guidance by noting it handles multiple pages at once and blocks private/internal hosts, but does not explicitly compare with sibling tools like scrape_page or read_url. The context of 'several pages' implies when to choose this over single-URL tools, though a more explicit recommendation would strengthen this dimension.

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