DELETE /licenses/{id}

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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false, openWorldHint=true, so the safety profile is fully covered structurally. The description adds nothing of its own: it does not say what deletion cascades to (seats, assigned users), whether it is soft-delete/restorable, or that a confirmation string may be required. It does not contradict annotations, but it contributes no behavioral context.

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?

It is short, but it wastes its only content on duplicated route text and OpenAPI generator boilerplate ("Generated from Snipe-IT OpenAPI operation licensesid-3"). The verb is front-loaded, yet nothing functionally useful follows it.

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, open-world delete with no output schema, an agent needs to know the consequences and irreversibility of the operation. Annotations cover the safety flags and the schema covers both parameters, but the description supplies no operational context (cascade behavior, error conditions, restore path).

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%; the schema already states that id is the numeric license ID (not name) and that confirm must be exactly "YES" when SNIPEIT_CONFIRM_WRITES is true. The description adds no additional parameter meaning, so the 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 restates the title and name verbatim ("DELETE /licenses/{id}") and adds a redundant path fragment "/licenses/:id". It does convey a verb and resource, but there is nothing to distinguish it from the many sibling license operations (snipeit_gen_licensesid, _1, _2, seats, etc.) beyond the HTTP method.

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?

No guidance on when to use this delete versus sibling license endpoints, no prerequisites (e.g., must the license have no checked-out seats?), and no mention of alternatives. The only usage hint comes from the schema's confirm parameter, not the description.

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