DELETE /hardware/{id}

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 covered externally. The description adds nothing beyond that — it does not say whether deletion is permanent or soft (relevant given the sibling snipeit_gen_hardwareidrestore exists), nor what happens to checked-out assets, licenses, or audit history attached to the asset.

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?

Very short and front-loaded, but the second sentence ('Generated from Snipe-IT OpenAPI operation hardware-delete') adds no actionable information and merely restates the endpoint as a generated artifact name.

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 mutation in a toolset containing both snipeit_delete_hardware and snipeit_gen_hardware_delete, the description needs to explain the difference and the soft-delete/restore semantics. It omits all of that, leaving ambiguity an agent cannot resolve from the description alone.

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%, so the schema fully documents both 'id' and 'confirm'. The description adds no syntax or format detail beyond the schema, which is the baseline expectation when schema carries the load.

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 ('Deletes a specific asset') with the endpoint path, so the basic action is clear. However, it does nothing to distinguish itself from sibling tools like snipeit_delete_hardware, snipeit_gen_hardwareidrestore, or the raw request tool, leaving an agent unable to tell which delete endpoint to pick.

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 versus the near-duplicate snipeit_delete_hardware, no mention of the confirm='YES' requirement, and no note about the restore alternative. The agent must infer everything from the endpoint string.

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