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

No annotations exist, so the description carries the full disclosure burden, and it does substantial work: it names the grouping key (currency), the returned components (normal/special/total cash DPS plus event counts), and explicitly warns that DPS is not dividend yield. It omits pagination behavior and does not state permissions, but for a read-style 'Get' tool this is well above average disclosure.

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?

Front-loaded with the core purpose in the first clause, followed by two short supporting sentences. The 'DPS is not dividend yield' clarification earns its place; only the stray line-break punctuation slightly hurts readability.

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 annotations and no output schema, the description compensates reasonably by naming returned fields, but it still leaves an agent without pagination/response-shape or auth context, and its silence on the get_dividends sibling is a real gap given the near-identical name.

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 100%, with all three parameters documented including as_of and symbol formats, so the baseline is 3. The description adds only the ex_date window semantics, which is scope rather than parameter syntax; no additional per-parameter meaning is supplied.

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 and resource with scope ('trailing-12-month cash dividends per share, grouped separately by currency'), so an agent knows exactly what it retrieves. However, it never distinguishes itself from the sibling get_dividends, leaving the two plausible candidates for the same request ambiguous.

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 the inclusion window (ex_date > window_start_exclusive and ex_date <= as_of_date), which is definitional scope rather than guidance on when to pick this over get_dividends or get_dividend_calendar. No prerequisites, no when-not, no named alternative.

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