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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), so the description only needs to add context. It does: results are limited to public articles, the URL must be canonical, and the payload structure is enumerated (title, authors, dates, section, keywords, image, ordered paragraphs). It does not describe failure modes for paywalled or malformed URLs.

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?

Two sentences, no filler. The action and input are front-loaded, followed by the return contents and the differentiating usage note. Every clause carries information.

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?

For a single-param fetch tool with an output schema and read-only annotations, this is nearly complete. The return values are actually already covered by the output schema, making that enumeration slightly redundant, and edge-case behavior (paywall, redirects, invalid canonical form) is unstated.

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 exists and schema description coverage is 100% ('Canonical NYT article URL'), so the baseline is high. The description reinforces the constraint by emphasizing the canonical form, but adds no further format detail (e.g., expected URL shape or path pattern).

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 and resource ('Fetch a public New York Times article') and pins the input to a canonical URL. It also distinguishes itself from the headline-oriented sibling by saying 'use this when you need the full article rather than a headline,' so an agent can separate it from nyt_headlines without opening any schema.

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?

Gives a clear selection condition: full article versus headline. It stops short of naming the alternative tool (nyt_headlines) or stating what happens with non-canonical or paywalled URLs, so the routing guidance is strong but not exhaustive.

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