get_equities_earnings_calendar

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint. Description adds value beyond annotations by specifying free/all plans, coverage of fiscal year companies, REIT exclusion, and ~3 months accumulated data. No 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?

Efficiently structured: brief summary, search term list, pairing suggestion, scope, plan support, parameter details. No redundant sentences; each part adds 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?

Given the existence of an output schema, the description does not need to explain return values. Covers input details, scope, exclusions, and integrations. Complete for a read-only query tool.

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 fully explains both parameters: date format (YYYYMMDD or YYYY-MM-DD, returns latest when omitted) and code (5 digits, 4-digit padding). Adds concrete usage guidance beyond the schema's basic type definitions.

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 (決算発表日), with a specific verb and resource. It includes Japanese keywords for search relevance and distinguishes from siblings by focusing on earnings calendar, which is unique among sibling tools.

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?

Provides explicit when-to-use with example search terms and a pairing suggestion (get_markets_short_sale_report). Mentions scope (March/September fiscal year, REITs excluded) and plan support. Lacks explicit when-not-to-use alternatives, but the tool is unique in its domain.

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