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

Annotations already declare readOnlyHint and idempotentHint, so safety is covered; the description adds genuine value by specifying the output format (compact Markdown table with named columns) and the batch ceiling of 20. It does not state what happens on oversized batches, invalid tickers, or partial failures, which is the remaining gap for a batch tool.

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?

Two sentences, zero waste: the first front-loads what the tool is and what it returns, the second immediately routes usage. Every clause carries information an agent needs.

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?

With no output schema, the description takes on the burden of describing the return value and does so concretely (Markdown table columns plus breadth summary). Combined with the batch limits and usage routing, an agent has everything needed 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?

Schema coverage is 100% and the single parameter's schema description already states '1 to 20 tickers in standard market notation' with examples. The description's '1 to 20 symbols in a single request' largely restates that, adding no notation or format detail beyond the schema, so the baseline 3 applies.

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 and resource — a multi-ticker batch comparison table for 1–20 symbols — and enumerates the returned fields (price, change, % change, day range, volume) plus a breadth summary. The closing clause explicitly separates it from single-ticker deep dives, so an agent can distinguish it from get_quote or analyze_ticker without opening any 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?

Gives a clear positive condition (multi-symbol portfolio or watchlist checks) and an explicit exclusion (not single-ticker deep dives). It does not name the specific sibling tool to use for the single-ticker case, leaving that mapping to inference, which keeps it just short of a 5.

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