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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds real behavioral context: only 'public' body paragraphs are served (implying paywalled content is excluded) and a 'canonical' URL is required, which tells the agent what it will and won't get back.

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 front-loaded sentence that states action, scope, and input constraint with zero filler. Nothing to trim.

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 values need no explanation, and annotations cover the safety profile. The description supplies purpose and input constraint; the only minor gap is not naming the sibling alternatives an agent might confuse this with.

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 0% and the single parameter is just 'url' typed as string. The description partially compensates by constraining the value to a canonical Daily Maverick article or opinionista URL, but gives no format example or guidance on non-canonical/redirect URLs.

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 (Extract) and resource (metadata and public body paragraphs) scoped to one Daily Maverick article or opinionista URL. This clearly separates it from the dailymaverick_headlines/news/sections siblings, which return lists rather than a single article 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?

It implies usage ('for one canonical ... URL') but never states when to choose this over dailymaverick_news or dailymaverick_headlines, nor what makes a URL canonical versus non-canonical. The condition is implied rather than spelled out.

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