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

Annotations already carry readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds valuable context beyond those: live sourcing from MarketBeat's daily ratings tables, US-listed coverage by default (NYSE, Nasdaq, NYSE American, OTC), and the note that the combined feed also carries Toronto/London listings — which explains why us_only exists. No contradiction with annotations.

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 dense paragraph that front-loads the core purpose and returns fields before moving to usage examples, filters, and sourcing. Every clause earns its place and the information density is high without being padded, though it is slightly long.

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?

There is no output schema, so the description correctly explains the returned fields (ticker, brokerage, analyst, ratings, price targets). It covers filters, coverage universe, sourcing, and the us_only default. Minor gaps are unspecified ordering/pagination behavior and no explicit routing away from the sibling analyst_ratings_for_symbol, but for a read-only, fully-documented-parameter list tool this is quite 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 coverage is 100%, so the schema fully documents all four parameters (limit, action, symbol, us_only) with descriptions and an enum for action. The description's mentions of filtering with `action` and narrowing with `symbol` merely reinforce the schema rather than add meaning, so the baseline of 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?

The description names a specific resource ('Today's US stock analyst upgrades and downgrades, market-wide') and a specific scope (every ratings action published this session, with ticker, brokerage, analyst, old/new rating and price target). It states the exact return fields, which distinguishes it from the single-symbol sibling analyst_ratings_for_symbol by being market-wide by default.

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 lists four explicit natural-language queries that trigger this tool ('which stocks were upgraded today', 'analyst downgrades today', 'today's price target changes', 'what did analysts initiate coverage on') and tells the agent how to filter (action enum) or narrow (symbol). It does not explicitly name the sibling alternative or state when NOT to use it, so it stops 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.