passgage_list_holidays

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits, but it only repeats schema capabilities. It does not mention response format, sorting behavior, default pagination limits (though schema does), side effects, or any other operational details beyond the literal list action.

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, efficient sentence that concisely conveys the core action and two key optional features. It is appropriately sized for a simple list operation and contains no fluff or redundant information.

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 straightforward list tool with a fully documented input schema and no output schema, the description is minimally adequate. It provides the essential purpose but omits potential context like the nature of holidays, default sorting, or mention of related get_holiday for single-item retrieval, which would aid an agent in selecting and invoking the tool correctly.

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%, with each parameter (page, filters, per_page) having explicit descriptions. The tool description adds only 'optional filtering and pagination', which is a high-level summary of the schema but not new semantic detail. This aligns with the baseline of 3 for well-documented schemas.

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 'List holidays' with an explicit verb and resource, and additionally mentions optional filtering and pagination, which are key behaviors. However, it does not distinguish this tool from other list_* tools or the related get_holiday tool beyond the resource name, so it lacks explicit sibling differentiation.

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 guidance is provided on when to use this tool versus alternatives, such as get_holiday for a single holiday or create/update/delete for mutations. The description only mentions features (filtering, pagination) without explaining suitable contexts or exclusions.

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