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

No annotations are provided, so the description must carry behavioral transparency. It adds the performance trait 'Cheaper than calling get_market_detail in a loop' but does not disclose potential limits on the number of tickers, pagination, error behavior, or response format. For a simple read operation, this is adequate but not fully transparent.

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, well-structured sentence that front-loads the purpose and adds a cost-saving hint. Every word earns its place, and there is no redundant information.

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?

The tool is simple with schema covering both parameters, and the description names the key use case. However, without an output schema or mention of return structure/limits, an agent might not fully anticipate the response shape. Given the similarity to get_market_detail, this is a minor gap, making it slightly above average but not fully complete.

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 description coverage is 100%, so both 'tickers' and 'depth' are already documented in the input schema. The description adds no additional meaning beyond the phrase 'by ticker list,' which merely echoes the schema. It does not explain the relationship between parameters or provide usage syntax beyond what is in the schema.

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's function: 'Fetch many markets at once by ticker list.' It names a specific verb ('fetch'), resource ('markets'), and method ('by ticker list'), and distinguishes it from the sibling tool get_market_detail by emphasizing the batch nature and cost advantage.

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 explicitly provides guidance by comparing to get_market_detail: 'Cheaper than calling get_market_detail in a loop.' This gives a clear when-to-use context. However, it does not mention alternative batch tools like get_markets or scan_markets, nor when not to use it, so it misses explicit exclusions.

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