rm_list_holidays

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the scope that both company and regional holidays are listed, which is useful, but it does not disclose pagination, date-range behavior, or response characteristics. With annotations covering mutation safety, a 3 is appropriate.

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?

Single six-word sentence with no filler. It is fully front-loaded and every word earns its place. No structural wasted.

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 simple list tool with no required parameters, an output schema, and read-only annotations, the description is minimally viable. However, it leaves out whether the optional date parameters are meant to filter the holiday list and when to use this versus single-holiday retrieval, so an agent must infer those details from the schema and sibling names.

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 0% description coverage and the description does not mention the optional from_date/to_date parameters at all. The parameter names themselves are self-explanatory, but the description fails to compensate for the lack of schema descriptions or date-format 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 uses a specific verb and resource: 'List company and regional holidays.' It clearly identifies the operation and scope, and its purpose is distinct from sibling tools like rm_create_holiday, rm_update_holiday, and rm_get_holiday.

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 usage guidance is provided. The description does not state when to choose this list tool over rm_get_holiday for a single holiday, nor does it mention any filtering behavior or exclusions. Usage is only implied by the tool name and description.

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