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

Annotations only supply readOnlyHint=true, so the description carries most of the burden and does so well: it discloses data-quality limits ('stored IV contrasts are not verified observed before/after IV crush', 'legacy historical proxy distribution', comparability notices) that an agent needs before trusting results. It does not cover rate limits or error behavior, so not a 5.

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 overview sentence is front-loaded and the six bullets are parallel and structured, so the length is justified by six distinct modes. Density and jargon make it heavy to parse, but there is little filler.

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?

No output schema exists, so the description must convey what comes back, and the per-kind bullets do describe the outputs conceptually (premium ratio, z-score, percentile; GEX by DTE bucket). It is complete enough to call the tool, though it leaves return formatting and pagination unspecified.

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% so baseline is 3, but the description adds real semantic depth to `kind` by explaining what each enum value computes (e.g., jump vs baseline-diffusion decomposition, gamma flip and walls by DTE bucket) rather than just restating the enum. `symbol` and `apiKey` gain nothing beyond the 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 opening sentence gives a specific verb+resource ('Get earnings analytics for a symbol across six lenses') and the bullets define each of the six kinds with concrete, domain-specific detail. It is clear what the tool does, but it does not distinguish itself from overlapping siblings such as get_vrp, get_expected_move, or get_strategy, which cover some of the same ground (vrp, expected_move, strategies).

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 kind list implies when each mode is appropriate, and there are interpretive caveats ('inspect historical_context and method notices before interpreting comparability'), but there is no explicit when-to-use or when-not-to-use guidance, and no routing versus siblings like get_vrp or get_expected_move that appear to duplicate kinds here.

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