Create a holiday

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

Annotations already signal that this is a mutation (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds little beyond restating the action; it does not disclose side effects, permissions, idempotency, or other behavioral traits that would enhance 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 a single, front-loaded sentence with zero unnecessary words. It conveys the essential purpose efficiently.

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 7 parameters, the schema thoroughly documents each one, mitigating the need for a verbose description. However, the description lacks context on how optional targeting parameters interact (e.g., everyone vs user_ids), which prevents a perfect score. Overall, it is sufficient given the schema richness.

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?

All 7 parameters have schema descriptions (100% coverage), so the schema carries the semantic load. The description itself adds no parameter-specific details, which aligns with the baseline score of 3 for high schema coverage.

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 verb 'Adds' and the resource 'holiday to the workspace calendar', making the tool's function unmistakable. It also distinguishes itself from sibling tools like clockify_list_holidays and clockify_delete_holiday through its specific create action.

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 does not provide explicit when-to-use guidance or mention alternatives. Usage is only implied by the tool's name and the sibling context, which is enough for an obvious create operation but lacks any explicit recommendations or exclusions.

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