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

Annotations only declare read-only and open-world behavior; the description adds important domain-specific traits by naming paywall flags (is_accessible_for_free, paywalled, is_truncated) and noting served body paragraphs. This tells the agent that content may be truncated or gated, which is useful beyond what annotations provide. It does not cover rate limits or auth, but the paywall disclosure is substantive.

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?

The description is a single front-loaded sentence with no waste. It efficiently names the source, resource, returned content, and key paywall indicators. Every phrase 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?

Given the simple one-parameter schema, existing annotations, and an output schema, the description is nearly complete for an agent to invoke the tool. It communicates the resource and notable paywall/truncation behavior. The only gap is the absence of sibling-selection guidance, which is outside the strict return-value scope.

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 description coverage is 100%, and the single url parameter is already documented as the canonical SMH article URL. The description adds no additional parameter syntax, format, or constraints beyond the schema. Baseline 3 is appropriate when the schema fully documents the parameter.

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 identifies a specific resource and scope: one Sydney Morning Herald article's metadata and served body paragraphs. It implicitly distinguishes the tool from siblings like smh_headlines, smh_news, and smh_sections by focusing on a single article. It stops short of naming alternatives or using an explicit action verb, so it is clear but not maximally 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 description explains what the tool returns but gives no guidance on when to use it instead of siblings such as smh_headlines or other article tools. There are no stated prerequisites, exclusions, or alternative-selection conditions. An agent must infer usage from the tool name and content alone.

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