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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real context beyond that: it returns only what 'anonymous visitors' see, signaling no paywall/subscriber content and implying a public, session-less fetch. It does not mention rate limits or failure behavior, but the anonymous-access note is genuinely useful.

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?

A single well-formed sentence, front-loaded with the verb and resource, with no filler. Every clause 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?

With an output schema present, return-value detail is unnecessary, and the description covers purpose, input shape, and access scope. The 'access state served to anonymous visitors' phrasing is slightly ambiguous about what is omitted, but overall it is complete enough for a single-URL extractor.

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 coverage, so the schema already documents the url fully. The description reinforces 'one canonical' URL (single value, must be canonical thenationalnews.com), adding marginal meaning. Baseline 3 is appropriate when the schema does the work.

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 (Extract), resource (The National article metadata and body paragraphs), and scope (one canonical story URL). It is clearly distinguishable from siblings like national_headlines, national_news, and national_sections, which operate on listings rather than a single article's full body.

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 phrase 'from one canonical story URL' implies you must already have a specific article URL, which distinguishes it from feed-style siblings, but there is no explicit when-to-use vs alternatives guidance (e.g. use national_headlines to discover URLs first). Usage is implied rather than stated.

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