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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds a scope boundary (forward ex-dates are not served) but does not elaborate on return format, data freshness, or sources beyond what the schema and output schema imply; with an output schema present, a 3 is appropriate.

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 front-loaded with the resource definition, followed by scope boundaries and usage examples in compact sentences; every sentence adds information and there is no waste.

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 data-retrieval tool with full schema coverage and an output schema, the description covers what is returned, what is excluded (forward ex-dates), and when to use it. It leaves minor gaps around data recency and output shape, but those are not required given the 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% and the schema already describes entity, kind with its enum meanings, limit, and periods in detail. The description only restates 'Args: entity; kind = dividends | buybacks | actions' without adding new semantics, so it meets the baseline 3 for a fully documented schema.

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 names a specific resource (capital returns: dividend history, buybacks, splits, name changes) with a clear framing verb phrase, and lists exactly what records are returned. It is distinguishable from siblings like get_calendar or get_insider_trades.

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?

It provides explicit example questions that map directly to the tool (did X raise its dividend; is X buying back stock; has X cut it), which is strong when-to-use guidance. It does not name alternatives or when-not-to-use cases, keeping it below a 5.

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