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

Annotations only declare readOnlyHint=true, so the description carries the behavioral burden and does so richly: it explains the two non-merged data sources, the confidence field, the published_events_degraded pre-check ordering, the data source (issuer IR pages + SEC filing cadence), cost (FREE), and that caveats ride tool_notes.

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?

Dense but front-loaded – the core purpose and the critical 'NOT merged / never present estimate as announcement' warning come early. The response-shape enumeration and sourcing tail are useful but make it longer than strictly necessary; still, every clause adds routing or safety value.

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, yet the description enumerates the return fields (ticker, published_events, published_events_degraded, estimate, provenance_rule, note) and explains the semantics of the ambiguous ones. Combined with the scope caveat, an agent has everything needed to call and interpret it.

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?

Only one parameter, fully documented in the schema ('Issuer symbol.', 100% coverage), so the schema does the work. The description adds no ticker format, exchange, or resolution rules beyond what the schema states. Baseline 3 is appropriate.

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 ('Upcoming EARNINGS DATES for one issuer') with a clear scope qualifier, and explicitly distinguishes itself from get_economic_calendar (macro releases). An agent can tell it apart from the ~60 sibling tools without opening the 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?

Gives explicit when-to-use guidance ('prefer a published date yourself'), when-not-to ('never present the estimate as a company announcement'), and a hard scope boundary ('US domestic 8-K filers only'). The alternative tool is named by condition.

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