DELETE /statuslabels/{id}

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered structurally. The description adds nothing beyond them: no word on whether deletion is permanent, what happens to assets currently assigned that status label, whether a confirmation flow is enforced, or whether a failure is returned for in-use labels.

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?

Two sentences, with the actionable statement first and no padding. However, the second sentence ("Generated from Snipe-IT OpenAPI operation statuslabelsid-1") is boilerplate that conveys no information about behavior and could have been replaced with actual usage context.

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, open-world mutation with a conditional confirmation parameter and no output schema, yet the description never covers consequences, referential impact on assets, or the confirm requirement. For a delete operation the description should carry far more behavioral weight than a one-line restatement of the route.

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 only 50% and the description contributes nothing to the parameters. Crucially it never mentions the `confirm` parameter or the SNIPEIT_CONFIRM_WRITES gate — that context lives entirely in the schema, so an agent skimming the description would not anticipate the extra required string when write confirmation is enabled.

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 status label") and labels the endpoint path, so the agent knows exactly what it does. It does not distinguish itself from the many other statuslabel endpoints (list_statuslabels, get_statuslabel_assets, gen_statuslabelsid variants), but the verb 'delete' is a strong differentiator by itself.

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 guidance on when to use this versus alternatives such as snipeit_gen_statuslabelsid_1/_2/_3 or snipeit_raw_request, and no mention of prerequisites. The only routing signal is the HTTP verb in the title.

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