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

Annotations already cover read-only, idempotent, closed-world, non-destructive semantics, so the bar is lower. The description still adds real behavioral context: dates are market-data sourced, is_estimate=true entries should be treated as approximate, results are sorted by earnings_date ascending, and the tool is available to all tiers (an access constraint not visible in the annotations).

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?

Front-loads the one-line purpose, then uses short bullets for the parameter, return shape, sort order, and caveat – easy to scan. The per-field enumeration of results[] overlaps with the existing output schema, which is mild redundancy, but the bullets are compact and nothing is padded.

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 an output schema and full annotations already present, the description covers the remaining gaps an agent needs: the estimate caveat, sort order, tier availability, and window bounds. Only the absence of routing guidance relative to the other earnings/calendar siblings keeps it from a 5.

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 100% and the single 'days' parameter is fully documented in the schema (default 7, max 30). The description only restates that same default/max, adding no syntax or format meaning beyond the schema, so the baseline 3 applies.

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+resource ('upcoming earnings dates for stocks') with scope (the Stocklake universe), so an agent can tell what it returns without opening the schema. It doesn't explicitly distinguish itself from the nearby sibling get_earnings_intelligence or get_economic_calendar, which keeps it short of a 5.

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?

Usage is implied by the look-ahead window framing ('days: look-ahead window in days, default 7, max 30'), which tells the agent the tool answers forward-looking calendar questions. There is no explicit when-to-use/when-not or routing to the earnings-related alternatives, so guidance stays at the implied level.

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