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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower; the description still earns credit by disclosing the row semantics of the payload — one earnings row per quarter, epsBasis values (gaap/adjusted/null) and dateStatus values (reported/confirmed/projected). It does not mention pagination or result ordering.

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?

Two sentences, front-loaded with the core purpose before the field semantics. The second sentence is dense but every clause (epsBasis, dateStatus definitions) carries information an agent cannot get elsewhere.

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 no output schema, the description carries the return-value burden and does explain the earnings fields well, but it says nothing about the shape of dividend or split rows, row ordering, or how limit truncates results. For a 3-parameter lookup tool it is close to complete, with those gaps remaining.

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 documented in the schema, but limit (default 12, max 50) has no description anywhere. The description adds nothing about parameter behavior, so the baseline 3 applies given the schema is doing most of the work.

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?

States a specific verb and resource: 'Get dividends, stock splits, and earnings events for one company'. The three event categories make it distinguishable from siblings like company.financials, company.statements, and catalysts.event without opening any schema.

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 phrase 'for one company' implies the scope (single-symbol lookup) but no explicit when-to-use or when-not-to-use guidance is given, and no alternative sibling is named. An agent must infer that company.financials or market.catalysts are the wrong choices.

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