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

Annotations only state readOnlyHint and openWorldHint. The description adds valuable context: cost ($0.03), the fact that 'x711 is the browser — agent never touches it', the anomaly detection flags (JS-heavy SPA, Cloudflare challenge, CAPTCHA), and the exact return structure. 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 front-loaded with a punchy 'Give any agent eyes' and then systematically lists outputs, anomalies, and usage benefits. While slightly marketing-toned ('turns a blind agent into one that can observe anything'), every sentence contributes functional information. It is longer than typical but justified by the tool's complexity.

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 fully explains the return object: { title, meta, headings, body_text, links, forms, images, detected: {prices, emails, dates}, anomalies, note }. It also covers potential edge cases (anomalies), cost, and the complementary tool, making the description self-sufficient for an agent to invoke correctly.

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 description already explains the URL parameter (must be public http/https, SSRF-protected). The description only repeats 'Pass any public URL' without adding new semantic detail. 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 opens with a clear verb+resource: 'Pass any public URL → get back a structured intelligence report', specifying exactly what the tool does. It differentiates from sibling x711_agent_act by positioning itself as the 'see' half of a browser loop, leaving no ambiguity about its role.

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 explicitly says 'Pair with x711_agent_act to complete the full browser loop', naming the alternative for interaction. It also gives clear when-to-use context: 'No Playwright config. No browser infra to spin up' — indicating it replaces manual browser setup for observation. The phrase 'Pass any public URL' defines the required input condition.

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