nc_is_public_holiday

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

No annotations are provided, so the description carries full burden. It only states what the tool does but does not disclose the return format (e.g., boolean true/false), any edge cases, or error behavior. Without output schema, this is a significant gap for an agent to correctly interpret the result.

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 with no wasted words. It is front-loaded with the core action and subject, making it easy to scan.

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?

The tool is simple (one required parameter), but the description fails to specify the return value or behavior, which is essential given there is no output schema. The agent cannot know if it returns a boolean, holiday details, or something else, so completeness is only partially satisfied.

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 description coverage is 100%, and the parameter 'date' already has a clear description in the schema ('Date to check in YYYY-MM-DD format'). The tool description adds no additional semantic information beyond what the schema provides, so a baseline 3 is appropriate.

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 states a precise action ('Check') and a specific resource ('a specific date is a public holiday in New Caledonia'). It clearly distinguishes this from sibling tools like nc_get_public_holidays (which likely returns lists) by focusing on a single date.

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 usage for checking one date, which provides clear context. However, it does not explicitly contrast with alternative sibling tools (e.g., nc_get_public_holidays for a range), so it lacks explicit when-not guidance, but the context is still unambiguous.

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