news_crypto

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

No annotations are present, and the description only includes pricing and an API URL. It fails to disclose behavioral traits such as latency, caching, rate limits, or any side effects. This is a significant gap for a data retrieval tool.

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 short but includes irrelevant details like pricing and API URL. It does not front-load the primary purpose, and the extraneous content harms conciseness without adding value for tool selection.

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 simplicity of the tool (one parameter, no output schema), the description could adequately explain the tool's purpose. However, it lacks any mention of return format, data structure, or typical usage, leaving the agent without crucial context.

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 has one parameter 'limit' with a brief description ('条数(可选)', i.e., count optional). The description adds no further meaning, but schema coverage is 100%, so a baseline score of 3 is appropriate.

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 labels the tool as 'News' and '加密新闻' (crypto news), indicating it provides news about cryptocurrencies. However, it lacks a specific action verb (e.g., 'fetch', 'list') and does not distinguish it from sibling tools like 'news_global'.

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?

No guidance is provided on when to use this tool versus alternatives. Sibling tools include various news and crypto-related tools, but the description offers no differentiation or context for selection.

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