markets_snapshot

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

With no annotations, the description carries the full burden, but 'batched' and 'keyless' do disclose useful traits: one call returns many quotes and no API key is needed. It omits data freshness/quote delay, rate limits, and read-only confirmation, which are material for market data.

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?

One compact sentence with no filler, and the core resource leads. It is terse to the point of being slightly under-specified, but nothing is wasted.

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?

An output schema exists, so return shape needn't be explained, and the tool is low-complexity with only one optional param. Still missing are the semantics of 'detail' and any note on data freshness or how it differs from market_stress, which an agent needs to call it correctly.

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 single 'detail' parameter has 0% schema description coverage; only its default 'short' is visible, leaving valid values and the effect of a longer detail unknown. The description does not mention the parameter at all, so it fails to compensate for the coverage gap.

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?

Names the resource concretely (market quotes) and enumerates the covered asset classes: indices, commodities, fx, crypto. 'Batched' and 'keyless' distinguish it from a per-symbol quote tool, though it never contrasts with the adjacent sibling market_stress.

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?

There is no explicit when-to-use, when-not-to-use, or alternative named. The closest sibling, market_stress, is left completely unaddressed, so an agent cannot infer from the description whether to call this or that for market context.

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