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

With no annotations, the description carries the transparency burden. It discloses the content of the calendar (record dates, payment dates, etc.) but introduces ambiguity by pairing 'upcoming dividend events' with a from/to date range, leaving unclear whether the tool returns only future events or honors historical ranges. No information about pagination, ordering, or rate limits is provided.

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 compact at two sentences, front-loaded with the tool's purpose. The first sentence is somewhat redundant ('Stay informed...') but hardly wasteful, and the second sentence efficiently lists included data elements. Overall, it is concise and well-structured.

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?

Given the absence of an output schema, the description does enumerate the expected content (record dates, payment dates, etc.), which is helpful. However, the date-range behavior is ambiguous relative to the 'upcoming' framing, and there is no mention of company identifiers or pagination. This leaves the tool only partially complete for an agent to invoke correctly.

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 input schema provides descriptions for both parameters ('Start date' and 'End date'), achieving 100% schema coverage. The description adds no additional semantic detail beyond what the schema already states, so the 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?

The description clearly states the tool's function: accessing a comprehensive schedule of dividend-related dates for all stocks, including record dates, payment dates, declaration dates, and dividend yields. The verb 'access' and specific resource 'Dividend Events Calendar' distinguish it from siblings like getDividends, which returns individual dividend data.

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 implies usage for staying informed about upcoming dividend events, but it does not explicitly state when to use this tool versus alternatives such as getDividends or getEarningsCalendar. No exclusions or alternative-recommendation language is provided.

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