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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the useful constraint that only "public" articles are supported and that a canonical URL is expected, but says nothing about failure modes, rate limits, or access requirements.

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 that front-loads the action and resource, then appends the input requirement. No filler or redundancy.

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?

Because an output schema exists, return values need not be described, and the annotations cover the read-only safety profile. The description states what is extracted and the input requirement, leaving only minor gaps in usage routing and URL format guidance.

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?

With one parameter at 0% schema description coverage, the schema alone gives no guidance. The description compensates partially by clarifying the parameter is a "canonical article URL," which is meaningfully more specific than a bare string, but it offers no format example or validity rules.

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 ("Extracts") and resource ("metadata and readable body paragraphs from one public SBS News article"), which cleanly separates it from list-oriented siblings like sbsnews_headlines or sbsnews_news. It stops short of naming a sibling explicitly, so it is clear but not fully differentiated.

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 public SBS News article; provide its canonical article URL" implies the scenario (retrieve a single article's content), but there is no explicit when-to-use/when-not or reference to alternatives such as headlines or author tools. Usage is only implied.

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