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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds two genuinely useful behavioral facts beyond that: only US-listed tickers are supported, and fair value is present only 'when published' (i.e., conditionally null). It says nothing about latency, rate limits, or failure modes for unsupported tickers.

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 tight sentence with no filler, and the scope clause ('for one US-listed ticker') is placed at the end where it qualifies the whole list. It loses a point only because the front of the sentence is a field dump rather than a statement of what the tool does.

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 carries the full burden of describing returns, and it does so adequately: score range (0-100), the five pillars, the four verdict values, confidence, conditional fair value, findings, earnings date, and URL. Missing only how to interpret the pillar scores and what the card looks like when data is thin.

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?

With one parameter at 100% schema coverage the baseline is 3, but the description adds real semantics the schema lacks: the ticker must be US-listed, and the call returns data for exactly one ticker (no batch). That constrains input choice in a way 'Ticker symbol, e.g. AAPL' does not.

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 is a noun-phrase enumeration of card contents rather than a verb+resource statement; the action ('get') is only recoverable from the name and title. It does scope the tool to 'one US-listed ticker', which helps, but it never distinguishes this composite card from siblings like get_analysis or get_valuation, whose outputs it partially overlaps.

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?

There is no statement of when to call this versus get_analysis, get_valuation, or rank_sector, and no prerequisites or exclusions. An agent must infer from the field list that this is the all-in-one summary card.

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