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

Annotations only cover readOnlyHint=true, so safety is handled; the description goes well beyond that by disclosing provenance semantics, that the two date sources are NOT merged, the meaning of the degraded flag, cost (FREE), and the underlying sources. It stops short of describing pagination/latency, but for a read-only data lookup this is substantial disclosure.

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-loaded with the core purpose, then provenance, then the return shape, then scope and sibling differentiation. Dense with jargon and several back-to-back constraints, but each sentence carries distinct operational information and nothing is redundant.

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, and the description compensates by enumerating the return object fields ({ticker, published_events, published_events_degraded, estimate, provenance_rule, note}). Combined with the provenance rules, scope, and sibling exclusion, an agent has everything needed to call and interpret it correctly.

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% and there is a single required ticker parameter, so the schema already documents it fully. The description adds only the framing that the result is scoped to 'one issuer', which is marginal but consistent. 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?

Specific verb+resource ('Upcoming EARNINGS DATES for one issuer') with an explicit scope and an explicit sibling exclusion ('Distinct from get_economic_calendar (macro releases)'). An agent can distinguish it from macro-calendar and corporate-events siblings 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?

Gives explicit when-to-use and when-not guidance: 'prefer a published date yourself', 'never present the estimate as a company announcement', 'Read published_events_degraded before reading the note as an issuer fact', plus the SCOPE constraint (US domestic 8-K filers only). Routing and handling conditions are all stated rather than implied.

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