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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the detail about returning source dates for events, which is useful but does not disclose other behaviors like result limits, pagination, or handling of missing data. Given the strong annotation coverage, the description provides only modest added value.

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 a single, efficient sentence that front-loads the action and key details. It has zero waste and is immediately understandable, which is ideal for an AI agent scanning multiple tool definitions.

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 simple, read-only tool with annotations covering safety, the description is nearly complete. It states what events are returned and the scope (one company). The lack of an output schema is acceptable for a straightforward getter. Minor gaps like pagination or time-range behavior are not critical given the tool's simplicity and the limit parameter.

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 67% (symbol and exchange are described; limit is not). The description does not explain any parameters beyond what the schema already provides. The limit parameter is self-explanatory with its default and bounds. The description adds no parameter-specific detail, so it relies on the schema, which is adequate but not enhanced.

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: retrieving dividends, stock splits, and earnings events for a single company, including each event's source date. This distinguishes it from siblings like company.financials or company.profile, which cover different data. The verb 'Get' and specific event types make the purpose unambiguous.

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 provides clear context by specifying 'for one company,' implying it is not for multi-company queries. However, it does not explicitly name alternatives or state when not to use it. Since the purpose is distinct among siblings, the context alone is sufficient, but it lacks explicit exclusionary guidance.

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