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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is partly covered; the description still earns credit by disclosing the cascade side effect on attached expenses and the mandatory user-confirmation gate, neither of which is in the annotations. It omits behavior on a nonexistent id (error vs. silent no-op), which would have completed the picture.

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?

Three short sentences, front-loaded with the destructive action, then the cascade consequence, then the confirmation precondition — each sentence carries distinct decision-relevant information with no filler.

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?

Covers the essential facts for a one-parameter irreversible delete: what it destroys, the ripple effect on expenses, and the confirmation requirement, and no output schema exists to explain. Minor gap is the lack of stated behavior for an invalid or already-deleted id.

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 coverage is 100% and the single 'id' parameter is documented in the schema as 'ID of the stay to delete.' The description only restates 'by id' and adds no format, source, or lookup guidance, so the schema carries the load and baseline 3 applies.

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?

States a specific verb and resource ('Permanently delete a stay by id') and immediately distinguishes its blast radius from the sibling delete_expense by explaining that expenses are cascade-deleted rather than independently removable.

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?

Gives a clear precondition for invocation ('call this tool only after the user has explicitly confirmed the deletion'), which is exactly the guidance an agent needs for an irreversible operation. It stops short of explicitly naming alternatives such as delete_expense for removing only an expense without removing the stay.

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