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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds a genuine output constraint — no winner verdict and no buy/sell/hold advice — which is not derivable from annotations. It says nothing about auth requirements, rate limits, or what happens with an unconfirmed ticker.

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 filler. The trigger condition comes first and the output restriction second, both earning their 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?

With an output schema present, return-value explanation is not required, and the description covers trigger, scope, dimensions and output guardrails. It is slightly thin on what happens when a ticker is invalid or not covered, which matters for an openWorld multi-input tool.

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 0% for the single tickers array, so the description must carry the load. It does: it states the 2–6 ticker range the array enforces and adds the qualifier "confirmed," implying tickers must be validated before comparison — a semantic the schema's regex alone does not convey.

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 (compare) and resource (stock tickers) plus the exact scope (two to six confirmed tickers) and the dimensions compared (valuation, growth, quality, market metrics, assumptions, coverage). This multi-ticker comparison framing inherently separates it from single-ticker siblings like get_stock_valuation and get_stock_fundamentals.

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 an explicit trigger ("Use this when the user asks to compare...") and a behavioral exclusion ("Do not declare a universal winner or give buy, sell, or hold instructions"). It does not name competing siblings such as screen_stocks or analyze_my_portfolio, so the agent must infer the boundary between comparison and screening.

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