get_economic_calendar

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

No annotations are provided, so the description carries the burden. It discloses the return type ('Economic events with dates and importance') and parameter defaults, but does not mention read-only behavior, pagination, timezone, or error handling. For a simple read tool this is adequate but not deeply transparent.

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 well-structured: one-line purpose, a 'Use this tool when' list, and compact arg/return notes. Every sentence adds value, no fluff, and details are front-loaded.

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?

For a two-optional-param read-only calendar tool, the description covers intent, use cases, args, and return content. It lacks edge-case details like timezone handling or default date range length, but overall it is sufficient for correct invocation.

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?

The schema provides only titles and defaults with 0% description coverage. The description compensates by specifying date format (YYYY-MM-DD) and semantic defaults ('today', '~1 week out'), which are not in the schema. This materially helps the agent use the parameters correctly.

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 states a specific verb ('Get') and resource ('macro economic-event calendar'), with concrete examples (CPI, FOMC, jobs reports) that distinguish it from sibling tools like get_earnings_calendar. The purpose is unambiguous.

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 lists when to use the tool: upcoming macro events, next CPI/FOMC/NFP, and event risk beyond earnings. This provides clear guidance and implicitly contrasts with earnings-related sibling tools, making when-not-to-use evident.

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