Economic Release Calendar

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

Annotations declare readOnlyHint=true, and the description reinforces this by describing a read-only calendar query. It goes beyond by detailing what is not included (FOMC meetings), explaining importance tiers with examples, and noting default time ranges. No contradictions.

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 concise (4 sentences) and well-structured, starting with the core purpose and then adding relevant details. Every sentence adds value: purpose, exclusions, defaults, and usage tips. No fluff.

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 key aspects: what the tool returns (publication dates, FRED series, importance tiers), what it excludes, and default behavior. However, it does not explicitly describe the output format (e.g., array of objects). Given no output schema, a hint about structure would improve completeness.

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 parameter descriptions. The description adds context by explaining defaults (30-day window, max 100 results) and the practical use of minImportance to filter market movers. While not repeating schema, it enriches meaning with usage examples.

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 'Get the economic release calendar' for US macro data, specifying it includes scheduled and recent publication dates, FRED series, and importance tiers. It distinguishes from sibling GetEconomicIndicator and explicitly excludes FOMC meetings, which are handled by another tool.

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 provides explicit when-to-use guidance, including defaults (next 30 days), filtering with minImportance (high for market movers), and a clear alternative: use GetEconomicIndicator to fetch actual data after release. It also warns that FOMC meetings are not included, directing to the Fed's calendar.

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