Holiday, shopping and events calendar

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds real value by disclosing the default window (next 90 days) and the shape of what comes back, including derived fields like 'days until' and hashtags. It does not mention rate limits or result-set size caps, which keeps it below a 5.

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, both dense with information, and the core capability plus return contents lead before the usage nudge. No filler or redundant restatement of the name.

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?

With no output schema, the description usefully describes what each result contains and states the default range, which is enough to call it correctly with zero required parameters. Minor gap: it never explains how minImpact or categories affect results, though the enums are self-evident.

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 71%, so most parameters are already documented in the schema (from/to/year/regions/includePast all have descriptions). The description reinforces the date-range and default behavior but adds nothing about minImpact or categories, leaving it at the baseline for this coverage level.

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?

States a specific verb+resource ('List holidays, shopping days, religious and cultural events') with scope ('any date range and region') and even enumerates the returned fields (dates, days until, promotion timing, content angles, hashtags). An agent knows exactly what this tool produces without opening the schema.

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?

Gives explicit timing guidance ('Use this before planning any campaign'), which positions it ahead of siblings like content_plan and start_campaign. It stops short of naming those alternatives or stating when-not to use it, so it is clear context rather than full routing.

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