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

Annotations cover safety (readOnlyHint, openWorldHint), and the description adds genuinely useful context beyond them: only "public body paragraphs" are served, implying paywalled/restricted content is excluded, and that metadata is included. It does not describe pagination or throttling, but the paywall scoping is a meaningful disclosure.

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 with the resource and scope front-loaded and no wasted words.

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 carries the return shape, and annotations carry the safety profile, so the description's job is mainly purpose and scope, which it covers. The paywall scoping note is a bonus; only minor gaps (e.g., behavior for non-canonical URLs) remain.

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 single url parameter is fully documented in the schema, so the baseline is 3. The description adds only the "canonical" qualifier already present in the schema and does not extend parameter meaning.

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 uses a specific verb ("Extract") and resource ("metadata and the public body paragraphs") and scopes it to "one canonical Daily Maverick article or opinionista URL," which implicitly separates it from the list-oriented siblings (headlines/news/sections). It stops short of naming a sibling, so a 4 rather than 5.

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?

There is no explicit when-to-use or when-not-to-use guidance and no alternative named. The single-URL scope hints at usage but the agent is left to infer that this is the per-article fetch tool versus dailymaverick_headlines/news.

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