release_calendar

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

No annotations are provided, so the description carries the full burden. It states the tool shows scheduled releases but does not explicitly disclose that it is read-only, nor does it mention any limitations or side effects. The default and max for days_ahead are noted, but more transparency (e.g., 'this is a read-only operation') would improve the score.

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 extremely concise with two sentences and parameter documentation. It front-loads the purpose and example, with no wasted words.

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?

Given the tool's simplicity (1 optional parameter, no required inputs, output schema exists), the description provides all necessary context. It covers the tool's purpose, the parameter, and provides an example query, making it complete for an agent to select and invoke correctly.

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 0%, so the description must compensate. It fully explains the 'days_ahead' parameter with purpose ('How many days forward to look'), default (14), and maximum (90), adding significant meaning beyond the schema's type and default.

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 uses specific verbs ('Show', 'scheduled') and clearly identifies the resource ('US economic data releases') and scope ('over the coming days'). The example query distinguishes it from sibling tools like list_indicators (list all indicators) and get_indicator (specific details).

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 explicitly states the use case with an example question, implying when to use this tool. It does not explicitly state when not to use it, but the sibling tools provide clear alternatives, making the guidance sufficient.

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