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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds behavior the annotations cannot: pagination is snapshot-bound (page 1 must be reused for later pages) and results are descriptive rather than predictive. It still omits the cost/size characteristics of an 11-parameter, likely wide result set.

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?

Three short sentences, no filler, and the operational rule (snapshot reuse) is stated plainly. The opening sentence is dense domain jargon ("provenance and coverage") that costs more parsing effort than the space it saves, but overall sizing is appropriate.

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 an 11-parameter tool with 9% schema coverage and no output schema, the description should carry much more: it never clarifies the duplicated paging controls, the two symbol parameters, or what fields the returned directory exposes. An agent must guess at most parameters before its first call.

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 9% — only "path" is documented — and 11 parameters exist with none required. The description explains only the snapshot parameter's provenance role; symbol vs target_symbol, season format, the date range, and the overlapping limit/page_size and page/offset controls are left entirely unexplained in both schema and description.

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?

"Retained earnings events and sector × market-cap comparisons" names the resource and the two content modes, but there is no verb and no statement of what is actually returned (a list of events? a comparison table?). An agent cannot tell from this sentence how earnings_history differs from siblings like research_company or compare_symbols.

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 only procedural guidance is "For page > 1 reuse the snapshot returned on page 1", which is genuinely useful usage instruction, and the closing caveat implies the tool is for descriptive reading. There is no when-to-use / when-not-to-use versus the sibling research and comparison tools, and no guidance on when to pass symbol versus target_symbol.

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