get_us_price

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

Discloses data source (Yahoo Finance, max 15-min delay) and lists all returned fields. No annotations provided, so description carries burden; adequately transparent for a read operation.

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?

Well-structured with summary, examples, fields, and args. Slightly verbose due to bilingual text, but front-loaded and each part adds value.

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?

Has output schema so return details are covered; description adds additional context not in schema. Complete for a single-parameter stock price tool.

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?

Only parameter 'ticker' lacks schema description (0% coverage), but the description adds full context: 'US 티커' with examples 'AAPL', 'TSLA', etc., fully compensating.

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 it retrieves US stock price snapshots for NYSE/NASDAQ, distinguishes from siblings like get_price (likely other markets) by specifying US market via yfinance.

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 example queries ('AAPL price') and specifies data fields returned, implying use for US stock queries. Lacks explicit when-not or alternatives, but context from sibling names helps.

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