check_holiday

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states the basic action and format, but does not mention what the tool returns, how it handles invalid inputs, or any limitations. This is a significant gap in transparency.

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 concise and front-loaded with the purpose. The additional format information is compact and earned, with no redundant or filler content.

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 and the presence of an output schema, the description provides sufficient invocation details (date format and country code). It lacks broader usage context, but the output schema covers return value details, making the description adequately complete for this low-complexity tool.

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 input schema has 0% description coverage, so the description must add parameter meaning. It does so by specifying the date format (YYYY-MM-DD) and giving country code examples (US, CA, GB), which provides essential context beyond the bare schema fields. It is not exhaustive but meaningfully compensates for the schema gap.

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 the tool's purpose: 'Get holiday information for a specific date and country.' It uses a specific verb and resource, and the date/country scope differentiates it from the unrelated siblings web_search and roll_dice.

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?

Usage is implied from the purpose (use for holiday information), but there is no explicit guidance on when to use this tool versus alternatives or any exclusions. The format hints (date format, country code) provide some usage direction, but not enough to warrant a higher score.

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