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

With no annotations, the description carries the full burden and does disclose meaningful behavioral traits: cost ($0.01 per call), no API key required, the upstream source (Tencent qt.gtimg.cn) and a Nasdaq fallback for US tickers. It omits rate limits, error/empty-symbol behavior, and latency characteristics, but the disclosed operational context is well above average.

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?

It is essentially one dense, front-loaded block that packs cost, output fields, market coverage, batching, auth and data source into a few clauses with no filler. It is slightly run-on, but every clause earns its place.

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 single-parameter tool with no annotations and no output schema, the description does the needed work: it enumerates returned fields (compensating for the missing output schema), covers auth, cost, symbol formats and data provenance. The only real gap is failure/edge-case behavior for invalid or empty symbols.

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 coverage is 100% for the single parameter, so baseline is 3, but the description adds symbol-format guidance beyond the schema example — prefix conventions for A-shares (sh600000, sz000001), HK (hk00700) and US (usAAPL or plain AAPL) plus comma batching. Note the schema example uses a different style (600519.SS, 00700.HK), which is a minor inconsistency the description does not resolve.

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?

States a specific verb+resource ('Real-time stock quotes') and enumerates the returned fields, making it clearly distinguishable from siblings like exchange_rates or sec_edgar_search. An agent can identify the tool's function without opening the schema.

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 explains how to call it (comma-separated symbols) and what markets are covered, but never states when to prefer it over alternatives such as exchange_rates or when it would be inappropriate. Usage context is implied rather than explicit.

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