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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context about which metrics come back, but says nothing about result ordering, the 100-item cap, or the default limit of 25, which matter for a list tool.

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?

A single dense but well-structured sentence that front-loads the resource and then the returned metrics; there is no filler. It is long, but almost every clause carries information the agent needs to judge relevance.

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?

With four optional params, no output schema, and modest annotation coverage, the description does well on the returned metrics but leaves the list behavior underspecified — default page size, sort direction, and whether the results are a ranked table or per-fund objects are all unstated.

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 50%: family and symbol carry descriptions, while sort and limit are undocumented in the schema. The description partially compensates by listing 'annualized distribution rate', 'trailing 12-month yield' and 'one-year total return', which give the agent a hint at what sort=distribution_rate and sort=total_return mean, but it never connects them to the parameters explicitly.

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 the concrete resource (option-income/covered-call ETF distributions) and enumerates the specific data fields it returns (latest payout, next payout, frequency, distribution rate, TTM yield, 1-year total return), with representative issuers and tickers. It is clearly distinguishable from the sibling dividend tools, though it never uses an explicit verb like 'list' or 'returns'.

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 scope implies when it applies (option-income/covered-call ETFs rather than ordinary dividend payers), but it never states when to prefer this over get_dividend_profile or get_dividend_changes, and gives no exclusions or prerequisites. Usage is inferable from the domain vocabulary rather than stated.

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