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

No annotations are provided, so the description carries the full burden. It implies a read-only operation ('Retrieve') and highlights the batch behavior (single request, multiple companies), but it does not disclose any potential limitations such as rate limits, maximum number of symbols, or data freshness. For a simple read tool, this is adequate but not rich in behavioral detail.

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, with the primary action and scope in the first sentence. It is well-structured and front-loaded, and the second sentence adds a brief use-case rationale without unnecessary verbosity. Every sentence 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 simple tool with a single, fully documented parameter, the description covers the core action and use case. There is no output schema, so the description should ideally specify return values more precisely, but 'market capitalization data for multiple companies' implies a collection of records. It lacks explicit details on the response format, but given the tool's simplicity, this is a minor gap.

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% with 'symbols' described as 'Comma-separated list of stock symbols'. The description adds little beyond the schema, merely reinforcing that multiple companies are supported. It does not provide additional meaning about formatting, examples, or constraints, so it meets the baseline without exceeding it.

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 action ('Retrieve market capitalization data') and the scope ('for multiple companies in a single request'), distinguishing it from single-company market cap tools. It also names the specific API (FMP Batch Market Capitalization API), leaving no ambiguity about the tool's function.

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 provides clear context for when to use the tool: when comparing market size of various companies simultaneously, streamlining valuation analysis. It does not explicitly mention alternatives or when not to use it, but the batch context is sufficient for a simple retrieval tool.

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