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

Annotations already declare readOnly/openWorld/non-destructive, so the bar is lower, and the description adds real substance: data provenance (stored SEC 8-K only), what is returned (filing links, extraction snippets, ingestion dates), and key limitations (incomplete coverage, dates can change, no provider fallback). That is meaningful disclosure beyond 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?

Four short sentences, front-loaded with the core action and scope, followed by provenance and caveats. Every sentence carries information and none is redundant with the schema or annotations.

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 steps in to say what is returned and flags coverage/volatility limitations, which is what an agent needs for a read-only lookup. The remaining gap is the undocumented limit parameter and the unclear relationship to get_company_earnings.

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 0%, so the description must carry parameter meaning. It conveys the ticker mode and the 1-90 day range (days_ahead), and implies discovery mode when no ticker is given, but 'bounded discovery list' is vague about what bounds it, and the limit parameter (default 10, max 20) is entirely unaddressed.

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+scope: upcoming company-announced US earnings dates, sourced from SEC 8-K filings, within a 1-90 day window. This is far more specific than the title. However, it does not explicitly differentiate itself from the close sibling get_company_earnings, so an agent must infer which one to use.

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?

Implies two usage modes ('a ticker or a bounded discovery list') and sets expectations with caveats ('not a complete market calendar', 'missing dates are unknown'). But it never names an alternative tool or states when-not to use it, leaving the get_company_earnings vs get_earnings_calendar routing to inference.

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