hostkit_delete_reservation

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

The description states the action is permanent and includes related records, but is minimal. With no annotations provided, the description should disclose more behavioral details such as irreversible nature, required permissions, or impact on associated invoices. It fails to sufficiently compensate for the lack of 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 sentence that conveys the essential action without any superfluous wording. It is appropriately concise for a simple delete operation.

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 simple delete tool with one parameter and no output schema, the description covers the basic purpose. However, it could be more complete by explicitly stating that the action is irreversible and clarifying what 'related records' entails (e.g., invoices, guests). It meets minimum adequacy but lacks full context.

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 single parameter 'rcode' is already fully described in the input schema. The description adds no additional meaning or context beyond what the schema provides. With 100% schema coverage, a 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 clearly states the action ('permanently delete') and the target resource ('reservation and related records'). It distinguishes from sibling tools like hostkit_cancel_reservation and hostkit_delete_invoice by specifying permanent deletion of a reservation with related records.

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 provides no guidance on when to use this tool versus alternatives such as hostkit_cancel_reservation. It does not mention prerequisites, constraints, or compare to related tools, leaving the agent without context for selection.

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