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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so safety is covered. The description adds real value with the data source (Yahoo Finance via yfinance, no API key), but omits important behavior: that the ticker symbol is optional in the schema yet obviously mandatory in practice, and what happens when no symbol is supplied.

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?

Purpose is front-loaded in the first sentence, event fields are stated in the second, and usage is scoped with a short bullet list. The bullets are slightly redundant with one another ('dividend history' vs 'dividend growth over time') but nothing is bloated.

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?

An output schema exists, so return-value explanation is not required, and the source/purpose are covered. What is missing is the operational minimum: which parameter identifies the company, what the period options mean for recency, and why an internal-fin filter like wholesaler_ids appears on a yfinance-backed tool — leaving the agent to guess at call shape.

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 reported as 0%, so the description is expected to carry parameter meaning, and it contributes nothing: neither 'symbol' nor 'period' (1y/5y/10y/max) is mentioned, despite 'full history' implying the max default. The schema also exposes unrelated parameters (wholesaler_ids, exclude_fillers, mcp_prompt_id) that the description never reconciles with a simple public corporate-actions fetch.

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 opening sentence names a specific verb (Fetch) and resource (cash dividends, stock splits, combined corporate actions) scoped to a ticker, which is clearly distinct from every sibling such as GetPriceHistory or GetFinancials. It stops short of an explicit sibling differentiation or stating that history is returned as a time series of events, so it is strong but not maximal.

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 three 'Use this tool when' bullets give concrete research contexts (yield inputs, dividend growth, split-adjusted returns), which is better than nothing. However, there are no exclusions and no named alternatives — for example, whether to use GetPriceHistory vs this tool for split-adjusted price work is never resolved.

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