获取股票信息

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

With no annotations, the description should disclose behavioral traits. It only states the action and exclusion. It does not mention whether the tool requires authentication, has rate limits, or if it is side-effect-free. The term 'get' suggests a read operation, but this is not explicitly confirmed.

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 sentence that efficiently conveys the tool's purpose and a key exclusion. It is front-loaded and contains no unnecessary words.

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 has no output schema, the description should explain what 'basic information' includes. It fails to do so, leaving the agent guessing about the return structure. Sibling tools are many, but no comparative guidance is provided. The description is too brief to fully inform an AI agent.

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 schema description coverage is 100%, so the baseline is 3. The description does not add new parameter-level semantics beyond what the schema already provides. It reiterates the overall purpose but does not clarify, for example, what format the symbol should take or how the market parameter impacts the query.

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 gets basic stock information by symbol and market. It explicitly excludes cryptocurrency. However, it does not differentiate from sibling tools like stock_prices or stock_indicators_*, leaving some ambiguity about what 'basic info' includes.

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 basic stock data and explicitly rules out cryptocurrency. However, it does not provide guidance on when to use this tool versus alternatives like stock_prices for price data or stock_indicators_* for technical indicators. No when-not-to-use advice is given.

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