List all available news categories with their recap timeframes.
Returns category codes that can be used with get_latest_news, get_news_recap,
and other tools. Each category includes its code, display name, and how
frequently recaps are generated.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Since no annotations are provided, the description carries the full burden. It discloses that the tool lists categories and their recap frequencies, and that output is used by other tools. It could mention return structure in more detail, but with an output schema available, the description adds meaningful context beyond schema.
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 two sentences with no wasted words. It front-loads the core purpose (list all available news categories) and immediately provides actionable context (returns codes for other tools, includes code, name, recap frequency).
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 zero parameters, 100% schema coverage, and an existing output schema, the description is complete. It tells the agent what information is returned and how it integrates with sibling tools, which is sufficient for correct selection and invocation.
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 description coverage is 100% with 0 parameters, so the schema already fully covers all input. The description adds value by explaining what the tool returns and how it relates to other tools, going beyond the empty schema.
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 lists all available news categories with their recap timeframes, which is a specific verb+resource combination. It distinguishes itself from sibling tools like get_latest_news and get_news_recap by clarifying it returns category codes used by those tools.
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 provides clear context for when to use the tool: before fetching news or recaps, as it returns codes needed by other tools. It does not explicitly state when not to use it or list alternatives, but the integration with sibling tools is well-explained.
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.