yahoo_news_article

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

There are no annotations, so the description carries the explanatory burden. It discloses that the tool fetches a single article, not a list, and discloses the content shape by enumerating headline, body, author, publish time, keywords, etc. It doesn't cover edge-case errors or rate limits, but for a simple read-only article retrieval, this is solid transparency.

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 concise and front-loaded. The first sentence identifies the domain and primary capability; the second adds a focused field inventory and input guidance. No wasted or redundant phrasing, and it reads quickly.

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 one-parameter retrieval tool, this is complete. There is no output schema, so the description adequately substitutes by enumerating the returned article components. It also explains the URL source pattern, making it easy for an agent to know how to obtain an appropriate canonical URL before invoking.

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 100%, so the schema already documents the URL parameter. The description adds useful nuance by emphasizing a canonical yahoo.com/news URL and by explaining where such URLs can be obtained, which helps the agent construct a valid argument.

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 opens with a clear noun phrase and then a specific verb-resource statement: 'Returns a single Yahoo News article's full content.' It enumerates the exact fields returned, making it unmistakable what this tool does and distinguishing it from the related category/home/search siblings.

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 clearly sets the expected input condition: a canonical yahoo.com/news article URL, and brings in context by noting that such URLs are typically returned by the home or category story streams. It doesn't explicitly name alternatives to avoid, but the stream-coupling is an effective use cue for the intended call pattern.

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