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

Annotations already declare read-only, non-destructive, idempotent, and open-world. Description adds that it returns title, link, description, source, sentiment, keywords, and mentions data source (NewsData.io). No contradictions. Does not detail pagination or rate limits, but annotations cover safety profile.

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?

Description is two concise sentences, front-loaded with the most important information (coverage and filterable fields). No wasted words.

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 (not shown), the description still lists return fields. No required parameters, 7 optional ones are all documented. Covers the essential aspects of the tool. Could mention pagination or maximum article limits, but adequate.

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% with well-described parameters. Description reiterates filterable fields but adds no additional meaning beyond what the schema provides. Baseline 3 is appropriate.

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?

Tool name 'news.global.latest' clearly indicates latest global news. Description states it retrieves news from 180k+ sources across 200+ countries in 70+ languages, with filtering options. Distinguishes from siblings like 'news.crypto.latest' (crypto-specific) and 'news.global.sources' (sources only).

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?

Description lists filtering capabilities but does not provide guidance on when to use this tool versus alternatives. No mention of when not to use or which sibling tools are better for specific scenarios (e.g., crypto news).

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