Search curated crypto news by keyword.
Searches across all news items for matching content. Returns headlines,
sentiment, categories, and sources.
Args:
query: Search keyword or phrase (e.g. 'ETF', 'SEC', 'Uniswap').
limit: Number of results to return (1-5, default 5).
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| query | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description needs to compensate for behavioral gaps. It clarifies that searches are across 'all news items for matching content' and lists return fields, but fails to disclose if results are real-time, cached, or have any rate limits. The tool is likely read-only, but this is implied rather than stated.
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 (4 lines of prose) and front-loaded with the core purpose. The docstring-style parameter list is efficient and adds necessary detail without redundancy. Every sentence serves a clear purpose.
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 tool's moderate complexity (2 parameters, no nested objects), the description covers the basic usage and output fields well. However, absence of any annotations or output schema details (despite the context signal indicating an output schema exists) leaves users uncertain about the result structure beyond what's listed. The context also lacks sibling differentiation beyond the basic purpose.
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?
Although schema description coverage is 0%, the description compensates well by explicitly listing the two parameters with examples ('e.g. 'ETF', 'SEC', 'Uniswap' for query) and a clear constraint (limit: 1-5, default 5). The examples and range add meaning beyond the basic schema fields.
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 uses a specific verb ('Search') and resource ('curated crypto news by keyword'), immediately clarifying the tool's scope. It distinguishes itself from sibling tools like get_latest_news (which likely returns recent articles without search) and get_news_item (which fetches a single item by ID).
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 search and explains return fields (headlines, sentiment, categories, sources), but does not explicitly state when not to use it or suggest alternatives like get_enriched_news for more detailed data or get_news_recap for summaries.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have distinct purposes, but get_enriched_news lacks clear parameters, making it ambiguous whether it returns a specific item, the latest, or category-based news. This could cause confusion with get_latest_news or get_news_item.
All tool names follow a consistent 'get_<noun>' pattern, making the naming predictable and easy to interpret.
Seven tools is well-scoped for a crypto news API, covering essential operations without being too few or too many.
The tool set covers the core workflow: listing categories, fetching latest news, searching, getting details, recaps, and premium enrichments. No obvious gaps for a read-only news service.