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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so safety and idempotency are covered structurally. The description adds a genuine behavioral constraint beyond the annotations — coverage is limited to US stocks — which warns the agent about possible empty results. It does not disclose data freshness/update cadence or how many analysts contribute, which would be the remaining useful context.

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?

A single sentence, front-loaded with what the tool returns, with every clause carrying information (rating, targets, implied move, buy/hold/sell distribution, US-only scope). No filler or redundancy.

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 bears the burden of describing the return shape, and it does so thoroughly by enumerating the target statistics and rating breakdown. Annotations cover the safety profile. Remaining gaps — data freshness and behavior when no analysts cover the symbol — are minor for a single-parameter read 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?

There is only one parameter (symbol) at 100% schema description coverage, so the schema fully documents it; baseline is 3. The description's 'for a US stock' adds a mild constraint hint about what the ticker should identify, but no format examples or validation expectations beyond 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 names the exact resource (Wall Street analyst consensus for a US stock) and enumerates the concrete outputs: consensus rating, 12-month price targets with mean/median/high/low, implied move, and buy/hold/sell counts. No sibling (quote, financials, earnings, insider trades, price history, SEC events, profile, superinvestors) overlaps with this data, so the agent can route unambiguously.

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?

Usage is implied by the data returned — an agent wanting forward-looking analyst sentiment would pick this — and the phrase 'for a US stock' implicitly scopes it to US-listed tickers. However, there is no explicit when-to-use guidance, no stated alternative (e.g., vs. get_stock_quote for current price), and no note on what happens for non-US or uncovered symbols.

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