获取股票信息

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It discloses input constraints (symbol and market) and the no-crypto limitation, but does not describe the return format, error behavior, data scope, or any side effects. This is a minimal disclosure for a tool with no annotation support.

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 a single, front-loaded sentence that states the main purpose and the key exclusion. Every word earns its place, with no redundant or filler content.

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 simple 2-parameter tool with an output schema, the description is acceptable but not rich. It covers the core function and the crypto exclusion, but lacks usage guidance relative to siblings and leaves 'basic info' undefined. Overall it is minimally complete given the low complexity.

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 input schema fully describes both parameters, including the supported market values and the no-crypto restriction. The description adds no parameter information beyond what the schema already provides, so the baseline score of 3 applies.

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 the tool retrieves basic stock information using a stock code and market, and explicitly notes that cryptocurrency is not supported. It identifies the action and resource, but 'basic information' remains somewhat vague and it does not strongly distinguish itself from sibling stock tools like stock_indicators_* or market_prices.

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 for stock information lookup and explicitly excludes cryptocurrency, which serves as a limited usage constraint. However, it does not mention any sibling alternatives or provide guidance on when to prefer this tool over other stock-related tools.

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