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

Annotations already declare readOnlyHint true and destructiveHint false, so the safety profile is covered. The description supplements this with ordering behavior, row fields, ex-date semantics, the possibility of future ex-dates, and the primary-ticker/issuer-level restriction—valuable context beyond the annotations.

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 four dense sentences with no filler. The core action and result ordering are front-loaded, followed by only high-value caveats that an agent needs before calling the tool.

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?

Even without an output schema, the description tells the agent what each returned row contains, how results are ordered, how filters apply, and a critical ticker restriction. Combined with the schema's parameter documentation, this is complete enough for correct invocation.

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%, so the baseline is 3. The description adds meaningful parameter semantics by stating that date filters apply to the ex-dividend date and that records are tied to the current primary ticker, clarifying startDate/endDate and ticker beyond their schema descriptions.

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 states a specific verb and resource: 'Get a company's stored declared cash dividends newest first.' It clearly identifies the row contents, ordering, and the primary-ticker constraint, and no sibling tool covers dividend history, so an agent can distinguish it.

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 clear invocation context: date filters apply to the ex-dividend date, records are issuer-level, and only the current primary ticker is valid. It does not explicitly name alternatives or say when not to use this tool, but that is a minor gap given no sibling directly overlaps.

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