get_equities_earnings_calendar

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

The description adds significant behavioral context beyond annotations: coverage of March/September fiscal year companies, REIT exclusion, ~3 month accumulation, and detailed cache fallback behavior. This aligns with the readOnlyHint, idempotentHint, and destructiveHint annotations without contradiction.

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 description is verbose but every sentence adds value, including usage keywords, parameter details, and caching notes. It is front-loaded with the main purpose. Minor restructuring could improve clarity, but it remains effective.

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?

Given the tool's complexity, annotations, and the presence of an output schema, the description covers all necessary aspects: what it does, when to use, how it behaves (caching, coverage), and parameter semantics. No gaps are evident.

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?

With 0% schema description coverage, the description fully compensates by detailing date format (YYYYMMDD or YYYY-MM-DD), default behavior ('Returns latest data when omitted'), code padding (5-digit, trailing zero for 4-digit), and search scope. This adds essential meaning 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 description clearly states 'Find upcoming/past earnings announcement dates' with a specific verb and resource. It distinguishes from sibling tools like get_earnings_this_week and get_earnings_results_this_week by emphasizing the calendar scope and pairing suggestions.

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 description provides explicit use cases (e.g., '決算発表, 決算日, ...') and pairing guidance with get_markets_short_sale_report. It also explains parameter behavior for date and code, including fallback caching logic. While it doesn't explicitly state when NOT to use, the guidance is comprehensive.

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