get_calendar

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

With no annotations provided, the description carries the burden of behavioral disclosure. It reveals the event categories, the look-ahead semantics, and the default/maximum window, which is meaningful context. It does not describe output ordering or edge cases, but the presence of an output schema reduces the need for that detail.

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 a single, focused sentence with no filler. The key information — what events, what window, and the bounds — is front-loaded and every word contributes value.

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 single-optional-parameter tool with an output schema, the description covers the essential semantics: event types, time horizon, and parameter bounds. It is slightly incomplete in not addressing ordering or how event categories are selected, 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 has 0% description coverage, so the description must fully explain the parameter. It does: 'within days' is described as the look-ahead window, with default 10 and max 60, adding the maximum constraint not present in the schema.

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 identifies the resource as upcoming macro events (FOMC, CPI, payrolls) and the look-ahead window, making the tool's function apparent. However, it lacks an explicit imperative verb like 'list' or 'retrieve', and does not explicitly distinguish itself from the sibling get_macro.

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 implies the tool is for fetching upcoming macro events within a configurable number of days, and gives useful default/max bounds. It does not mention when to prefer this tool over siblings such as get_macro or provide exclusions, so the routing guidance is only implicit.

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