get_upgrades_downgrades

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

With no annotations, the description carries the burden of behavioral disclosure. It reveals the output includes each entry's from/to grade and action, that results are most-recent-first, and that non-equity symbols return empty results. This gives meaningful behavioral context beyond the bare 'what it does'.

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 concise and well-structured: a one-sentence purpose, followed by essential identifier guidance and output behavior. Every sentence adds value, with no repetition of annotations or obvious filler.

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?

The description covers purpose, input constraints, asset-type limitations, and output ordering. Since an output schema exists, return-value details are unnecessary. The description plus schema fully cover the tool's use context.

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% for both parameters, and the schema already describes 'symbol' and 'limit' in detail. The tool description reiterates the symbol constraints already present in the schema, adding minimal new parameter-specific semantics, so the baseline of 3 is appropriate.

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 uses a specific verb ('Get') and clearly identifies the resource ('recent analyst rating changes (upgrades/downgrades)') and scope ('for a Yahoo symbol'). It distinguishes this tool from siblings like get_recommendations by focusing on rating changes with specific grade/action details.

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 gives explicit usage conditions: the symbol must be a native Yahoo ticker, not an ISIN/WKN/name, and users should call the 'search' tool first to resolve identifiers. It also states the tool is equity-only and empty for other asset types, providing clear context though not naming alternative tools explicitly.

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