get_market_snapshot

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly states 'Read-only — cannot place, modify, or cancel orders,' which is a key safety-relevant trait. It also discloses that it handles multiple codes. Further details about rate limits or auth are absent, but for a simple read-only snapshot, this is sufficient.

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 two sentences, front-loaded with the core purpose, and every word adds value. The safety note is concise yet important. Zero fluff.

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 tool with one parameter and an output schema, the description covers purpose, parameter format, and read-only behavior. No critical operational gaps. The output schema likely documents return fields, so omitting them here is appropriate.

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 0%, but the description compensates by explaining the 'codes' parameter: it takes one or more stock codes, with concrete examples like 'US.AAPL' and 'US.TSLA'. This adds meaning beyond the bare schema, though it does not specify all accepted formats or limitations.

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 fetches current price, volume, % change, and other live data for stock codes, with specific examples. The verb 'get' and resource 'market snapshot' are specific, and the scope (one or more codes) distinguishes it from siblings like portfolio exposure or screeners.

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 implicitly defines when to use the tool: whenever live market data for specific stock codes is needed. It provides example code formats, making the intended use clear. It does not explicitly name alternative tools for exclusion, but sibling context makes the differentiation obvious.

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