search_crypto_news

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

No annotations are provided, so the description carries the full burden of disclosing behavioral traits. It confirms a read-only search across seven sources, but it fails to mention result ordering, pagination, deduplication, or response format, leaving significant ambiguity about what the agent can expect.

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 a single, front-loaded sentence with no filler or redundant information. It conveys the essential function and scope in minimal words, earning full marks for conciseness.

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 no output schema and no annotations, the description is too sparse to provide complete context. It does not describe the result structure, the names of the seven sources, or how this search differs from related news tools, making it insufficient for an agent to fully anticipate the tool's behavior.

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?

The input schema already provides complete descriptions for both parameters, including the keyword format example and the limit default and range. The description adds only the phrase 'by keywords,' which does not meaningfully enhance parameter understanding beyond the schema, earning the baseline score for high schema coverage.

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 action ('search'), the resource ('cryptocurrency news'), and the scope ('by keywords across all 7 sources'). This distinguishes it from sibling tools like get_crypto_news or get_defi_news, which appear to be category-based feeds rather than keyword searches.

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?

The description implies usage for keyword-based news searches, but it does not explicitly state when to choose this tool over alternatives such as search_historical_news or get_breaking_crypto_news, nor does it mention any exclusions. The phrase 'across all 7 sources' provides some context but no direct comparison.

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