加密货币走势图

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

With no annotations, the description carries the full burden of behavioral disclosure. It only mentions generating an ASCII chart and does not reveal whether it fetches live market data, the data source, potential errors, or the format of the output beyond being an ASCII chart. This is minimal transparency.

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, focused sentence with no redundant words. It efficiently communicates the core purpose. Though it could be more informative, the structure is appropriately concise and front-loaded.

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?

The tool lacks annotations and an output schema, so the description must compensate. It does not clarify how it differs from the similar draw_ascii_chart tool, nor does it explain data source, update frequency, or error behavior. Given the simplicity of the tool, the description is still insufficiently complete for correct invocation without further 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 already provides 100% description coverage for both parameters (bar and symbol), so the baseline is 3. The description does not add any additional meaning or context for the parameters beyond what the schema already documents.

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 generates ASCII trend charts for cryptocurrencies, with the explicit verb '生成' (generate) and resource '加密货币的 ASCII 走势图' (crypto ASCII trend chart). This distinguishes it from the broader draw_ascii_chart sibling and other crypto price 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?

No guidance is provided about when to use this tool versus alternatives. It does not mention that draw_ascii_chart is for generic charts or that crypto_prices provides price data instead. The description only states what the tool does, not when it should be selected.

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