DELETE /maintenances/{id}

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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false and openWorldHint=true, so the safety profile is covered by structured data. The description adds nothing beyond that – it never mentions irreversibility, what happens to associated records, or that SNIPEIT_CONFIRM_WRITES may demand confirm="YES"; the second sentence is pure generator boilerplate.

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 actionable clause is front-loaded and short, but the second sentence ("Generated from Snipe-IT OpenAPI operation maintenancesid") is low-value boilerplate that does not help an agent decide or invoke. Two sentences, one of which does not earn its place.

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?

This is a destructive write with no output schema and a mandatory confirmation parameter, yet the description explains none of that: not the confirm gate, not the error/404 behavior, not whether the deletion is a soft or hard delete. For a destructive 2-parameter tool the description should carry far more weight.

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 100%, and both parameters (id, confirm) carry their own descriptions including the exact const "YES". The description only echoes the {id} path token and adds no format, validation, or confirm-flow detail, so 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?

The description states a specific verb and resource ("Delete a maintenance") and the path makes the identifier explicit, so an agent knows exactly what will be removed. It does not, however, distinguish this tool from the several near-identical maintenance siblings (snipeit_gen_maintenances_1, _copy, _copy_1, snipeit_list_maintenances), which forces the agent to guess.

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 statement of when to use this versus the other maintenance endpoints, no prerequisite or permission context, and no mention of the confirm parameter's role. The only usage signal is implicit in the word "Delete".

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