get_current_price

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

No annotations are provided, so the description carries the full burden. It discloses that the price is the last-traded price and that batch queries up to 200 symbols are supported. However, it does not mention error behavior, return structure, or whether prices are delayed/real-time, which would improve 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 compact, front-loaded with the core purpose, and then gives exactly the parameter details needed. No filler or redundant information is present.

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 single-parameter price lookup with an output schema available, the description covers purpose and parameter semantics adequately. It could be slightly more complete by noting expected return value shape or potential errors, but those are partially addressed by the output schema.

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 schema only defines 'symbols' as a string with no description. The tool description fully compensates by specifying comma-separated tickers, a maximum of 200 symbols, no market prefix, and concrete KRX/US examples. This adds substantial meaning beyond the raw 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 states a specific action and resource: 'Get the current (last-traded) price for one or more symbols.' This clearly distinguishes the tool from related siblings like get_recent_trades or get_orderbook by focusing on the current price 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?

The description implies usage when a current price is needed and provides input constraints, but it does not explicitly say when to prefer this over alternatives such as get_candles or get_stock_info. No exclusion rules or alternative routing are given.

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