get_equities_earnings_calendar

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

Annotations already provide readOnlyHint and idempotentHint. The description adds value by disclosing that the tool covers March/September fiscal year companies, excludes REITs, accumulates ~3 months of data, and explains parameter behavior (returns latest when date omitted, searches accumulated data for code).

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 well-structured with clear sections and front-loaded purpose. While slightly long, every sentence adds value and there is no redundancy.

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 simplicity (2 parameters, output schema present), the description covers all essential aspects: data coverage, parameter handling, and pairing suggestions. No gaps remain.

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%, but the description compensates by defining date format (YYYYMMDD or YYYY-MM-DD) and code format (5 digits, 4-digit padded with trailing 0), plus behavior when omitted.

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 the tool finds upcoming/past earnings announcement dates, using specific verbs and resource. It distinguishes from siblings by mentioning a paired tool (get_markets_short_sale_report) and provides Japanese terms and use cases.

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 gives clear use cases (e.g., 'earnings calendar', '今週決算がある銘柄') and pairing guidance. It does not explicitly state when not to use, but given no sibling earnings tools, this is sufficient.

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