crypto_news

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

With no annotations, the description carries full responsibility. It discloses the source (Reddit), cost ($0.000 per call), and return format (headlines with fields). It implies read-only behavior but does not explicitly state idempotency or side effects, missing a chance for full 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 well-structured: purpose first, then usage condition, returns summary, and a complete example. No unnecessary sentences; every part earns its place.

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 no output schema, the description provides a full example response, sample parameter values, and cost details. It covers all necessary information for an agent to understand input, output, and usage context, making it highly complete.

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%, but the description adds value via the example response, which demonstrates parameter usage (e.g., 'currencies': 'ETH') and clarifies sort order options. The example helps an agent understand the expected output and parameter interplay.

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 retrieves 'latest crypto news and community sentiment from r/CryptoCurrency for any token', specifying the verb (get/retrieve), resource (news and sentiment), and scope (any token). It distinguishes from siblings like token_market_data and fear_greed_index, which focus on different 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 when: You need recent news headlines or community sentiment for one or more crypto tokens', providing clear context. While it doesn't list when not to use, the sibling tools cover other domains, so the guidance is sufficient.

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