get_prices

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

Annotations already declare this as a safe read-only operation. The description adds the useful constraint of a 200-symbol maximum and the input format, but does not discuss edge cases such as invalid symbols or behavior on exceeding the limit. This is adequate but not rich.

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 and front-loaded: the first sentence states the core function, and the second line gives the critical parameter format. Every word earns its place with no redundancy.

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?

For a simple one-parameter read-only tool with an output schema, the description, annotations, and schema together provide sufficient context. The symbol format, limit, and read-only nature are all covered, and the sibling list clarifies the tool's niche in the broader API.

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?

With 0% schema coverage, the description compensates by explaining that the 'symbols' string is comma-separated and provides concrete examples for both Korean and US markets. This adds essential meaning beyond the bare schema, though it stops short of covering every edge case like spaces or validation rules.

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?

Description clearly states the tool retrieves current prices for up to 200 symbols. The verb 'Get' and resource 'current prices' are specific, and the tool is distinguished from siblings like get_candles, get_trades, and get_orderbook by focusing on the current snapshot.

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?

Provides clear usage context by specifying the comma-separated symbol format and the 200-symbol limit. It does not explicitly contrast with alternative tools for historical data, but the wording 'current prices' implies the appropriate time-sensitive use case.

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