crypto_price

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

No annotations are provided, so the description carries full responsibility. It only includes pricing and an API URL, with no disclosure of behavioral traits such as read-only nature, latency, authentication needs, or side effects.

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 poorly structured: the first line mixes a title hint with pricing, which is not a proper description. The API URL is arguably extraneous for an AI agent. It lacks a clear, front-loaded statement of 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?

With no output schema and minimal description, the agent cannot understand what the tool returns (e.g., price, timestamp, currency). The description fails to compensate for missing structured information, making it inadequate for informed 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% (one parameter with description '交易对如 BTC/USDT'). The tool description adds no extra meaning to the parameter; baseline 3 is appropriate since the schema already documents it adequately.

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 includes '[Crypto] 加密行情' implying crypto price quotes, but lacks a clear verb+resource statement (e.g., 'Get current crypto price'). The presence of siblings like 'btc_price' and 'token_price' suggests differentiation, but the description does not clarify scope or uniqueness.

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 no guidance on when to use this tool versus alternatives (e.g., btc_price, token_price). There is no mention of appropriate contexts, exclusions, or prerequisites, leaving the agent without decision criteria.

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