search_holidays

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering safety and behavior. The description adds no additional context beyond 'search', such as what types of holidays are included or whether results are cached. Given annotations, the description contributes minimal extra insight.

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 short sentence with no waste. It is front-loaded with the key verb and resource. However, it could be slightly more informative without losing conciseness, e.g., specifying optional filters.

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 has 4 parameters (2 optional) and rich annotations, the description only covers the basic date range constraint. It does not explain how optional filters (instance, employee_id) affect results, nor clarify the source or scope of 'holidays'. The presence of an output schema partially mitigates, but the description is still incomplete for effective use.

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 should compensate. It only hints at 'date range', corresponding to start_date and end_date, but provides no details on format or semantics. The optional parameters instance and employee_id are completely unaddressed. The description adds little beyond the schema.

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 'search' and the resource 'holidays', with a date range constraint. It is specific enough to distinguish from generic search tools like search_records, but lacks explicit differentiation from other holiday-related tools.

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 finding holidays within a date range, but does not explicitly state when to use this tool versus alternatives like search_employee or search_records. No exclusions or alternative references are given.

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