public-holidays.getPublicHolidays

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. However, the description adds no extra behavioral context (e.g., rate limits, required authentication, or format of results), and it fails to clarify how the tool receives country and year despite the empty schema. No contradiction exists, but it does not enrich the annotation-provided information.

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, concise sentence that states the core function with no filler. It is easy to parse and front-loads the key information.

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, the description is too thin. The empty schema combined with the description's claim of country/year inputs leaves the agent without a clear calling convention. The output schema exists, but the input gap is critical; the description does not resolve how to specify required data, making the tool effectively unusable without guessing.

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 zero properties, yet the description mentions country and year as inputs. This is a major inconsistency: the description implies parameters that the schema does not define, and it omits any format, type, or encoding details. Baseline for 0 params is 4, but the description's vague mention without schema support fails to give the agent usable semantics.

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 a specific verb (Get), resource (public holidays), and scope (for a country and year). It distinguishes this from sibling getAvailableCountries by implying the agent needs a specific country and year, making the purpose 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?

No guidance is provided on when to use this tool versus alternatives. It does not mention that getAvailableCountries should be called first to obtain valid country codes, nor does it specify any prerequisites. The agent is left to infer the relationship between sibling tools.

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