crypto-news-impact

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

No annotations are provided, but the description fully discloses data sources (CoinDesk RSS, CoinGecko), caching TTL (5 min), output fields (title, URL, timestamp, category, sentiment), and enrichment logic (asset-to-price mapping). This covers key behavioral traits beyond what annotations would typically specify.

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 4-5 sentences, front-loading purpose and data freshness. Every sentence adds unique information: source, TTL, output details, enrichment, usage guidance. No filler 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?

Given the single optional parameter and no output schema, the description thoroughly covers return fields, sentiment derivation, asset enrichment, and data provenance. For a news tool, this is complete and actionable.

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?

Only one parameter (limit) with schema coverage 100%, so baseline is 3. The description adds value by explaining the default (10) and the output structure (articles with enrichment), which helps the agent decide an appropriate limit.

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 specifies the tool fetches the latest crypto news from CoinDesk and correlates with live prices. It clearly states the verb (fetch), resource (news headlines), and enrichment (price correlation), distinguishing it from other crypto tools like sentiment indices or fundamental data.

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?

Explicitly says 'Use before any crypto research, portfolio review, or market sentiment task to understand what news is driving the market right now.' Provides clear context but does not mention alternatives or when not to use, preventing a score of 5.

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