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

With no annotations, the description carries the full burden. It mentions the output includes headlines, snippets, and URLs, which is useful. However, it does not disclose pagination behavior, date range semantics, or any limitations, leaving gaps for an agent.

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, two sentences, and front-loaded with the main purpose. Every line adds value without excessive detail or redundancy.

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?

While the tool is relatively simple and the schema covers all parameters, the description lacks usage context compared to sibling news tools. It does not mention pagination behavior or when to prefer this over searchCryptoNews, making it incomplete for fully informed tool selection.

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 parameters (to, from, page, limit) are well-documented in the schema. The description adds no additional param-specific meaning, such as the effect of date boundaries or pagination mechanics, which is consistent with the baseline score of 3.

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 clearly states the tool fetches cryptocurrency news with specific elements (headlines, snippets, URLs). It identifies the resource (crypto news) and action (access a curated list), but does not explicitly differentiate from sibling news tools like getGeneralNews or searchCryptoNews.

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?

No guidance is provided on when to use this tool versus alternatives such as searchCryptoNews for keyword-based queries or getGeneralNews for broader coverage. The description lacks any when/when-not or alternative recommendations.

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