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

With no annotations, the description must fully disclose behavior, but it is lacking. It mentions data fields but misleadingly says 'upcoming dividend payments' when the API likely returns historical data as well. There is no mention of pagination, default behavior, response structure, or error handling.

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 two sentences, front-loads the purpose, and avoids excessive detail. The phrase 'Stay informed' is slightly vague, but overall it is efficient and to the point.

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?

Without an output schema or annotations, the description needs to explain return values and behavioral context. It lists some fields but fails to clarify the response format, how empty results are handled, or the inconsistency between 'upcoming' and full dividend data. The description is incomplete for a tool with no output schema.

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% with both parameters described (symbol and limit with default/max). The description adds no additional parameter semantics beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 clearly states the tool provides dividend data for individual stock symbols, listing specific fields like record dates, payment dates, and declaration dates. However, it does not explicitly distinguish this from sibling tools like getDividendsCalendar or getDividendAdjustedChart, so it is clear but not fully differentiated.

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?

No guidance is provided on when to use this tool versus alternatives. The phrase 'for individual stock symbols' hints at a use case, but there is no explicit when-to-use or when-not-to-use, nor any mention of sibling tools like getDividendsCalendar for broader dividend calendars.

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