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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true), and the description adds genuinely useful behavior the annotations cannot convey: the is_truncated flag semantics and the fact that paywalled pages return only public text. This is exactly the kind of gotcha an agent needs before trusting the body content.

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?

One dense sentence with zero waste. The core return description is front-loaded and the paywall caveat follows immediately, so the agent absorbs the important behavior in a single read.

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, the description need not enumerate return fields, and it covers the one non-obvious behavior (paywall truncation). For a one-parameter read tool this is essentially complete, with only URL-format expectations unaddressed.

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%, so the description carries the full burden, but the single parameter (url) is self-explanatory and the description says nothing about it. It adds no meaning beyond the schema, though with one obvious parameter the practical gap is small.

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 names the specific resource (one The New Yorker article) and its scope (metadata and body paragraphs), which cleanly distinguishes it from siblings like newyorker_headlines, newyorker_news, and newyorker_sections. It lacks an explicit verb ('fetch'/'retrieve'), but the noun phrase is unambiguous about what is returned.

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?

Usage is implied by the single required url parameter: this is the 'get the full article by URL' tool, versus the feed/list siblings. However, it never explicitly states when to prefer this over newyorker_headlines or newyorker_news, nor any preconditions about which URLs are valid.

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