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

Annotations already declare it as read-only, idempotent, non-destructive, and open-world. The description adds context: it does not execute JavaScript, does not bypass access controls, and uses caching (fresh parameter). It also mentions URL validation against SSRF-sensitive destinations. No contradiction.

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 three sentences, each serving a purpose: stating the function, specifying constraints, and giving parameter advice. Front-loaded with purpose, no fluff.

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 simplicity (2 parameters, annotations, output schema present), the description covers all key aspects: purpose, constraints, parameter semantics, and behavioral traits. With output schema available, return values need not be described.

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 the schema already documents both parameters. The description reinforces usage (e.g., 'Pass url as an absolute public HTTP(S) URL' and guidance on fresh) but does not add significant new meaning beyond the schema. 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 clearly states the tool estimates words, characters, sentences, and reading time from a URL. It specifies the resource (URL content) and distinguishes it from siblings like web.url.text or web.url.extract by focusing on reading statistics.

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: only for public HTTP(S) resources, no JavaScript execution, no access control bypass. It also explains when to set fresh=true vs false. However, it lacks explicit mention of alternative tools.

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