yahoo_finance_calendar

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

With no annotations, the description must fully disclose behavioral traits. It only states what is returned, not whether the operation is read-only, has rate limits, authentication needs, or any side effects. The description lacks necessary behavioral context.

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 short—two sentences with minimal waste. The first sentence acts as a title, and the second describes the action. However, it could be more structured by front-loading the key action first.

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?

Despite having 7 parameters and no output schema, the description is minimal. It does not explain how the parameters work together, what the return format looks like, or how pagination via offset/limit behaves. A more complete description is needed for this complex 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 100%, so the baseline is 3. The tool description does not add any additional meaning or usage guidance beyond what is already in the parameter descriptions. It repeats the types (earnings, IPOs, etc.) but adds no new semantics.

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?

Description clearly states the tool returns Yahoo Finance calendar rows for earnings, IPOs, economic events, or splits. The verb 'returns' and resource 'calendar rows' are specific. However, it does not distinguish from the sibling tool 'yahoo_finance_calendars' (plural), leaving potential confusion.

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?

No guidance is provided on when to use this tool versus alternatives like 'yahoo_finance_calendars' or other Yahoo Finance tools. There is no mention of context, exclusions, or prerequisites.

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