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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds real value beyond that by specifying ordering ('newest first') and the breadth of the payload, though it does not say what is returned for a non-dividend-paying ticker.

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 resource and its scope, followed by a field list and then clarifying examples. Dense but every clause carries information; the field enumeration is slightly long but earns its place given no output schema.

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 output schema, the description compensates well by listing the returned fields and their order. The only gap is behavior for tickers with no dividend history and whether the profile returns nulls or errors, which is left unstated.

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%, so both parameters are already documented with examples and a 0-100 range. The description restates 'newest first' but adds no syntax or edge-case meaning beyond the schema. Baseline 3 applies.

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 ('get') and resource (one stock/ETF/fund's dividend record) and enumerates the exact fields returned: forward yield, payout ratio, safety grade, ex-dividend dates, fair value, raise/cut history. An agent can distinguish this from the sibling calendar and change-feed tools without opening the schema.

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?

Three concrete example questions ('does Coca-Cola pay a dividend', 'when is O's next ex-dividend date', 'has PepsiCo ever cut its dividend') clearly signal when to reach for this tool. It stops short of naming the sibling it should not be used for when the answer is a bare history delta, so it is not a full 5.

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