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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavior beyond them: the XBRL cash-flow source, newest-first ordering, and the sign convention (negative = cash outflow), which prevents misreading the values.

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?

Two short fragments that are entirely front-loaded with the resource and the most decision-relevant facts (source, order, sign). Zero filler; every clause carries information the caller needs.

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?

For a read-only tool with no output schema, the description covers scope, source, ordering, and value sign, which is nearly everything needed to call it correctly. Minor omissions remain, such as currency/units and whether amounts are total cash paid rather than per-share, but the core is complete.

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 ticker and periods are fully documented in the schema and the baseline is 3. The description adds nothing about parameter syntax or format (e.g., how periods interacts with the annual granularity), so no credit above baseline is warranted.

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 resource (annual cash dividends paid) and adds the data provenance (XBRL cash-flow tags) and ordering (newest first), so the agent knows exactly what is returned. No sibling covers dividends, so there is effectively no competing tool, but the description never names or contrasts an alternative explicitly.

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 definition of scope implies when the tool applies (annual dividend history), but there is no explicit when-to-use or when-not guidance and no reference to any sibling tool. With 23 sibling financial tools, a routing hint would have been valuable; usage is left to inference.

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