Toss Get Price Limits

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 limits are upper and lower, but does not specify what these limits represent (e.g., daily percentage bounds) or any prerequisites (e.g., symbol format, data availability). 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?

Single sentence with no wasted words, front-loading the verb 'Get' and the object 'upper and lower price limits'. Excessively concise yet clear.

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 one parameter, the description covers the core functionality but lacks details on output format, what the limits apply to (e.g., daily price change), and any limitations. Adequate for a simple tool but could be more informative.

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 has 0% description coverage for the only parameter 'symbol'. The description merely states 'for one KRX or US stock symbol', adding no semantic detail beyond what the schema's pattern suggests. Does not compensate for missing schema descriptions.

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?

Clearly states that the tool retrieves upper and lower price limits for a stock symbol, specifying the markets (KRX or US). This distinguishes it from siblings like toss_get_prices (which likely retrieves current price) and toss_get_stock_warnings.

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?

Implies usage context: when needing price limits for a single Korean or US stock. However, does not explicitly exclude other scenarios or compare with similar siblings, but the purpose is clear enough for an agent to infer appropriate use.

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