passgage_create_holiday

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention any side effects, permissions, or error conditions. Apart from implying a write operation, it reveals nothing about how the tool behaves.

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 extremely concise, using a single sentence with zero wasted words. However, it is so brief that it borders on under-specification, lacking even a hint of the data structure, but the text itself is well-structured and front-loaded.

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 an unconstrained nested data parameter, no output schema, and no annotations, this description is wholly inadequate. It does not explain what constitutes a holiday, what data fields are needed, or what the tool returns. An agent would struggle to invoke it 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?

The input schema documents a single 'data' parameter with a generic description and allows arbitrary properties. The description 'Create a new holiday' adds no information about what fields are required inside the data object. Since the schema effectively provides no structural constraints, the description offers insufficient meaning for correct invocation.

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 'Create a new holiday' clearly states the verb and resource, distinguishing it from get/update/delete/list siblings. However, it does not provide any additional differentiation or context beyond the generic create pattern, so it falls short of a top score.

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 guidance on when to use this tool versus alternatives, such as update_holiday for modifying existing holidays. The intended usage is only implied by the verb 'create', with no exclusions, prerequisites, or context provided.

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