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

Annotations already declare readOnly, openWorld, non-destructive and non-idempotent. The description adds useful context beyond them: up to 15 seconds waiting for network settle, public pages only, and per-call pricing including failed calls being free. It stops short of describing the returned structure or truncation behavior directly, relying on '/extract' for output semantics.

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 key differentiator and usage trigger are front-loaded, and the description is dense without obvious repetition. It is slightly run-on, especially the pricing and safety clauses appended at the end, but every sentence carries useful information.

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 four-parameter extraction tool with no output schema, the description covers the important operational facts: rendering behavior, latency wait, public-only access, failure guidance, and cost. It relies on the sibling '/extract' for exact output format, which is a minor completeness gap.

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 all four parameters are already documented in the schema. The description only supplies an example url and does not add meaning for format, section, or maxChars beyond what the schema provides. Baseline 3 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: rendering a page in a real browser and returning its text/Markdown. It explicitly contrasts itself with the sibling /extract tool, so an agent can tell the two apart without opening schemas.

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?

It gives an explicit condition for use: when /extract returns EXTRACTION_EMPTY or too little text for a page readable in a browser. It also states the public-page/no-login constraint, which tells the agent when this tool is not applicable.

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