Financial Calendar

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

Discloses that results may be truncated for large date ranges, which is beyond what annotations provide. No contradictions with annotations (readOnlyHint, etc.).

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?

Two sentences plus a list, well-structured and front-loaded with main purpose. Every part adds value with no waste.

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?

Covers categories, date range guidance, optional market filter, and truncation behavior. Output schema exists, so return values don't need explanation. Complete for a calendar 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 coverage is 100% with detailed parameter descriptions. The description adds minimal extra meaning (e.g., category lists with shorthand), but the schema already carries the burden.

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's purpose: 'Get finance calendar events by category and date range.' It lists specific categories and an optional market filter, distinguishing it from siblings like ipo_calendar.

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?

Explicitly advises keeping date ranges to 2 weeks or less and splitting longer periods into multiple calls to avoid truncation. Lacks explicit alternatives but provides practical usage guidance.

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