List holidays

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

Annotations already declare this a safe read-only operation. The description adds that both public and company holidays are included, but it does not disclose behavior such as date-range filtering, pagination, workspace fallback, or response format. This minimal addition does little to enhance transparency beyond 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 wasted words. It communicates the essential content (holiday types and workspace scope), though it is perhaps too terse to fully inform the user.

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 7 parameters and no output schema, the description is adequate but minimal. The schema covers parameter details, and the annotations cover safety, but the description does not mention return values or filtering capabilities, making it incomplete for a tool with this complexity.

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 all 7 parameters documented (to, from, page, limit, all_pages, page_size, workspace_id). The description itself adds no parameter-specific meaning, so the baseline of 3 is appropriate.

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 states what the tool returns: public and company holidays in the workspace. Although it lacks an explicit verb, the title 'List holidays' clarifies the action, and the description distinguishes this from sibling create/delete holiday tools by mentioning workspace configuration.

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?

There is no explicit guidance on when to use this tool versus alternatives. No mention of typical use cases (e.g., viewing upcoming holidays) or exclusions (e.g., use create_holiday for adding). The context is only implied by the tool's purpose.

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