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

Beyond readOnlyHint/openWorldHint, the description discloses the 50,000-character truncation ceiling, the exact response fields including `truncated`, and the billing model (7 credits per successful call, invalid input rejected before billing). Those cost and truncation semantics are real behavioral context an agent cannot get from annotations. It doesn't say how non-2xx pages, timeouts, or JS-rendered content behave.

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?

Front-loaded with purpose, then return shape, then cost — a sensible order with no filler. The field enumeration and the 50,000-character cap partly repeat the schema, a minor redundancy.

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?

With no output schema, the description correctly spells out the return object, which is its main job here, and adds billing and truncation notes. Gaps remain around error/HTTP-failure behavior and how content is extracted (e.g., JS-rendered pages), which matter for an open-world scraping 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?

Schema coverage is 100% and both parameters are fully described there, including the URL restriction set and maxChars range. The description only restates the 50,000-character cap, adding nothing beyond the schema, so the baseline 3 applies.

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?

States a specific verb+resource ('main content of one public page as Markdown') and the output format, so an agent knows exactly what comes back. It never distinguishes itself from close siblings like page-markdown, web-extract, or web-contents, which the agent must disambiguate itself.

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?

'One public page' implicitly signals a single-URL scope (not crawling or search), but no sentence says when to choose this over web-search, web-map, or page-markdown. Usage is inferable rather than stated.

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