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

The description says 'Read a web page' implying a harmless, read-only operation, but the annotations mark readOnlyHint=false and destructiveHint=true. This is a direct contradiction – the description gives no indication of destructive side effects or writes. Per the rubric, any contradiction with annotations forces a score of 1.

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 well-organized with a main sentence, use cases, a routing section, and an approval note. Each sentence carries useful information and the most important fact ('return content as clean markdown') is front-loaded. It's a bit verbose, but not bloated.

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?

The description covers when to use, what to expect, and some limitations, but it completely omits any mention of destructive behavior despite the annotation. It also doesn't describe return format beyond 'clean markdown' or address potential side effects. The contradiction makes it functionally incomplete for an agent to reason about.

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 description coverage is 100%, so both 'url' and 'companyId' are already fully described in the input schema. The description adds no extra parameter detail (e.g., URL formatting, security notes) beyond what the schema provides. 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?

The description states a specific verb ('Read') and resource ('web page') with the expected output ('clean markdown'). It also lists concrete use cases (analyze, summarize, extract information) and sets scope via page types. However, it doesn't explicitly name or differentiate from sibling tools like 'browse_url' or 'inspect_url', which are likely similar.

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 provides explicit when-to-use guidance ('Use when the user asks to read, analyze, summarize...') and clear when-not-to-use conditions ('NOT for pages requiring login or dynamic SPAs'). It also includes routing by content type. But it stops short of naming alternative tools for those exclusions, so the agent must infer what to use instead.

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