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

Beyond the readOnlyHint annotation, the description discloses return fields (title, description, link, source, publish date, category, country), pagination via nextPage token, and filtering behavior (business category filters out SEO/crypto-promo content). It also warns about zero results for wrong category guesses, adding significant behavioral context.

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 compact but information-dense, with a clear flow: purpose, filters, critical note, return fields, pagination, examples. Every sentence adds distinct value, and the front-loaded first sentence immediately establishes the tool's core function.

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?

No output schema exists, so listing return fields is essential—done. Pagination, parameter usage, and edge-case warnings (zero results) are covered thoroughly. With 6 optional parameters and rich examples, the description fully equips an agent to use the tool correctly in varied scenarios.

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 baseline is 3. The description adds value by illustrating parameter combinations with examples (query+category, query+country+category+language) and by emphasizing the business category behavior, which is critical for effective use. However, it doesn't deeply elaborate on type formats beyond what the schema already explains.

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 specific verb+resource: 'Get the latest global news headlines and articles' and clearly enumerates coverage areas (world news, breaking news, business/financial/stock-market). It distinguishes itself from sibling tools like crypto_news by stating 'global' and including multiple categories, making the scope unmistakable.

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?

Provides explicit when-to-use guidance with capitalized 'IMPORTANT' instruction for stock-market queries to pass category 'business', plus concrete examples for world market news and election news. It also implies alternatives by noting category behavior and omitting crypto, which differentiates from sibling crypto_news.

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