get_stock_quote

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

No annotations so description carries full burden. Describes successful return (dict with price, change, volume, etc.) and failure case (error key). Does not explicitly state read-only or idempotent, but behavior is clear.

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 Args, Returns, and Example sections. Every sentence adds value, though slightly verbose with docstring conventions.

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?

Complete for a simple tool: describes input, output, error handling, and provides example. No annotations needed; description covers all relevant aspects.

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% coverage; description fully compensates with format ('6-digit A-share code'), examples ('600519', '300750'), and context. Adds meaning beyond type alone.

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 'Get the real-time quote for a single A-share stock' with specific verb and resource. Distinguishes from siblings (get_financial_statements, get_industry_news) by focusing on quotes vs financials vs news.

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 and explains parameter format. Implicitly distinguishes from siblings via purpose. Lacks explicit when-not-to-use or alternative guidance.

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