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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds substantial behavioral context beyond the annotations: it renders JavaScript in a browser, returns partial success with a failed list, does not charge when every URL fails, and explains pricing and authentication requirements. There is no contradiction with 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 dense but every sentence earns its place: batching limit, JS rendering, contrast with url-extract, partial success and billing behavior, required parameter, pricing, and auth. It front-loads the core capability before commercial details and is well-structured for an agent to parse quickly.

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 and the presence of an output schema, the description covers all essential selection and invocation details: what it returns, how failures are reported, cost implications, required parameter, and authentication alternatives. An agent can confidently choose and call this tool without additional context.

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% and the schema already describes urls as 'URLs (comma-separated, max 5).' The description reinforces the comma-separated format and adds that each page returns clean text with its title, which gives the agent a clearer expectation of what the parameter input produces. This is modest value beyond the schema, so a 4 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 states a specific verb and resource: 'get each page back as clean text with its title.' It also clearly differentiates from sibling url-extract by noting it covers SPAs, dashboards, and app pages that 'url-extract deliberately refuses,' and by mentioning that url-extract is cheaper for single static pages.

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 explicitly tells when to use this tool versus url-extract: use it for JavaScript-rendered pages and batches up to 5 URLs, while choosing url-extract for a single static page. It also covers failure handling and free-call/pricing details, giving clear selection context.

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