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

Annotations already cover safety (readOnlyHint) and world scope (openWorldHint), so the bar is lower. The description adds real behavioral context beyond them: the upstream-error behavior for video-only and text-free pages, and the fact that body paragraphs are returned. It does not mention pagination or rate limits.

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?

Two compact clauses with zero waste; the core fetch behavior and its failure mode come first, followed by sibling routing. Everything earns its place.

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?

An output schema exists, so return values need not be explained. The description is complete for a single-URL article fetcher: it covers what is fetched, the input form, the failure modes, and how to find URLs first.

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?

Only one parameter with 100% schema description coverage, so the schema already documents it. The description reinforces 'canonical URL' but adds little syntax or format detail beyond the schema's own 'Canonical CNET article URL'.

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 (Fetch) plus the precise resource (CNET article metadata and body paragraphs) and the input form (canonical URL). This is clearly distinguishable from the headline/news discovery siblings it names.

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?

Gives explicit when-to-use (a canonical CNET article URL), when-not (video-only pages and pages without article text fail upstream), and names cnet_headlines, cnet_news, and cnet_sections as the discovery alternatives. Routing is unambiguous.

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