plu_delete_unavailability

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

Without annotations, the description must disclose behavior. It indicates the tool deletes data and mandates user confirmation, but does not explain side effects, authorization requirements, or whether the deletion is reversible.

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 very short (two sentences) and front-loaded, but it omits essential information. It is concise but at the expense of clarity and completeness.

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 one parameter, no output schema, and no annotations, the description is severely incomplete. It does not explain what an unavailability period is, how to get the ID, or what happens post-deletion. Sibling tools like 'plu_get_unavailabilities' exist but are not referenced.

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 has one parameter 'unavailabilityId' with no description. The tool description adds no meaning to this parameter, failing to explain what the ID represents or how to obtain it. Schema description coverage is 0%.

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 tool deletes an unavailability period, which is a specific verb+resource. However, it does not differentiate from the sibling tool 'plu_delete_availability' beyond the name, which could cause confusion.

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 includes 'IMPORTANT: ask user confirmation' as a usage instruction, but provides no guidance on when to use this tool versus alternatives, such as when to delete availability instead, or prerequisites.

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