accelo_delete_holiday

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

No annotations are provided, so the description carries the full disclosure burden. 'Delete' implies a destructive, likely irreversible mutation, but the description says nothing about required permissions, whether the deletion cascades to related records, or whether it can be undone. The '(Beta)' tag is a minor but real disclosure of stability status.

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?

Very short and front-loaded, with the purpose stated first. The docstring-style 'Args:' block is slightly noisy for a single parameter but wastes no meaningful space.

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 destructive single-parameter mutation with no annotations and no output schema, the description should at minimum cover permissions and irreversibility. Instead it leaves the agent with only the purpose and a restated parameter, which is thin for a delete operation.

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 must compensate. It does clarify that the single 'id' parameter is a 'Holiday ID to delete', adding semantic meaning beyond the bare integer 'Id' in the schema, but it omits where to obtain the ID or any format constraint.

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 a specific verb and resource ('Delete a holiday'), which cleanly distinguishes it from the sibling create/update/get/list holiday operations. It is clear what the tool does, though it never names those siblings explicitly to reinforce the distinction.

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 versus alternatives, no prerequisite such as fetching the holiday ID via accelo_get_holiday or accelo_list_holidays first, and no warning about irreversibility. The only usage signal is the operation name itself.

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