passgage_update_holiday

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It states 'Update an existing holiday' but does not disclose side effects, required permissions, whether the update is partial or full replacement, error behavior if the holiday doesn't exist, or any return value. This is a significant gap for a write operation.

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 sentence containing only the necessary information. It is concise, direct, and free of unnecessary elaboration, earning it a perfect score for conciseness.

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?

The tool is a simple update with two parameters, but the data object is open-ended (additionalProperties true), and there is no output schema. The description does not explain what fields are valid in data, whether the update merges or replaces, or what to expect in response. Given the lack of behavioral information and open-ended schema, the description is insufficient for an agent to fully understand the tool's behavior.

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 input schema covers both parameters (id and data) with descriptions, achieving 100% schema coverage. The description adds no additional parameter details beyond what the schema provides. Since schema coverage is high, the baseline score 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 'Update an existing holiday' clearly specifies the verb (update) and the resource (holiday), and distinguishes itself from create/delete/get/list operations. It directly states the action and target, leaving no ambiguity about its purpose.

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: use when an existing holiday needs modification. However, it does not explicitly mention alternatives like create_holiday for new holidays or delete_holiday for removals. There is no guidance on when not to use it or what prerequisites exist, so only implied usage is provided.

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