rm_create_holiday

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

Annotations already declare readOnlyHint=false and destructiveHint=false, indicating a mutating but non-destructive operation. The description adds no behavioral details beyond the act of creating, such as uniqueness rules, date validation, or side effects, but it does not contradict the annotations.

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 no padding. Every word serves a purpose and the core action is stated immediately.

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?

For a create operation with three parameters and zero schema descriptions, this description is incomplete. It does not specify date formatting, the meaning of end_date, or behavior on duplicate holidays, and the output schema only covers return values, not input semantics.

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 0%, so the description must compensate for documenting parameter semantics. It does not explain the expected date format, whether end_date creates a range, or any constraints on name. The parameter names are self-explanatory at a basic level, but key details are missing.

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 uses a specific verb and resource ('Create a new company holiday or non-working day'), making the tool's purpose immediately clear. It is easily distinguished from sibling tools like rm_update_holiday, rm_delete_holiday, and rm_list_holidays.

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 wording implies this is for creating a new holiday, which gives basic usage context. However, it does not explicitly state when to prefer this over alternatives or mention related tools such as rm_update_holiday for modifications.

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