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

Annotations already carry readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile needs no restatement. The description adds genuinely useful non-structured context: the data source (Yahoo Finance via yfinance) and that no API key is required, which tells the agent about auth and data provenance.

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 purpose, then return shape, then a scannable bulleted usage block, then source. Slightly padded by leading/trailing whitespace and line breaks, but every sentence carries information.

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 the brief return-field note is sufficient and no return-value detail is owed. Purpose, usage triggers and data source are all covered; only per-parameter guidance is absent, and the nested schema largely fills that gap.

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?

The report flags 0% schema description coverage at the top level, and the description mentions no parameter names, formats or defaults. However, the nested DividendsAndSplitsParams $defs do describe period, symbol and the other fields in detail, so the agent is not left blind; the description itself simply adds nothing here.

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 ('Fetch the full history of cash dividends, stock splits, and combined corporate actions for a ticker') and names the returned fields. This distinguishes it cleanly from siblings like GetPriceHistory and GetEarningsHistory.

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 'Use this tool when' block gives three concrete scenarios (dividend history/yield inputs, dividend growth research, split verification for returns). It gives clear positive context but never names an alternative tool or a when-not-to-use condition.

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