Earnings Calendar

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

ReadOnlyHint annotation already marks it as a read-only operation. The description adds context about the output including expected moves implied by options pricing, which is a key behavioral trait beyond the annotation. It does not mention pagination or edge cases, but the read-only status is established.

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 compact and well-structured: a one-line summary, a clarifying sentence, a usage trigger list, and a concise Args/Returns block. Every section earns its place without redundant phrasing.

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?

The description covers purpose, usage guidelines, parameter semantics, and return value. Since output schema is absent, the Returns statement fulfills that need. For a simple read-only calendar tool, this is complete.

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 has 0% description coverage and both parameters are undocumented in the schema. The description's Args section explains days_ahead as the number of days to look ahead with default 7, and min_market_cap as a minimum market cap filter in billions, providing essential semantics that compensate fully for the schema gap.

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 opens with 'Get upcoming earnings announcements'—a specific verb plus resource. It further elaborates that it shows companies reporting earnings in the upcoming period including expected move implied by options pricing, which distinguishes it from related tools like economic calendar or earnings history.

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 includes an explicit 'Use this tool when...' section listing concrete user intents: upcoming earnings, what companies report this week, earnings calendar. It doesn't mention when not to use it or alternatives, so it's clear context but lacks exclusions.

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