finance_stock

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

With no annotations, the description effectively conveys that this is a read-only query tool by listing output fields (price, PE, PB, dividend yield, technicals) and parameters. It does not disclose potential limitations like rate limits or data freshness, but the behavior is well-explained for typical use.

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 with a clear bullet list of modes and examples. It is front-loaded with the purpose, and every sentence adds value without 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?

Given the tool's complexity (7 parameters, multiple modes) and presence of an output schema, the description covers most scenarios. Minor omissions like limit and indicators parameters prevent a perfect score, but overall it is complete for a data query 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?

Schema description coverage is 0%, so the description must compensate. It explains keyword, symbol, date, days, and include through examples, but does not explicitly describe limit or indicators parameters, leaving gaps in parameter understanding.

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 clearly states 'Query A-share stock data' and lists multiple specific modes (search, latest quote, date-specific, history, with technicals, with fundamentals), which distinguishes it from siblings like finance_fund and finance_stock_screen.

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 provides explicit usage examples for each mode and notes that either keyword or symbol is required. However, it does not explicitly mention when not to use this tool (e.g., for in-depth fundamentals vs finance_fund) or highlight alternatives among siblings.

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