Create hardware

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

Annotations already disclose destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered externally. The description adds only the required body fields and says nothing about irreversible side effects, validation failures, permission requirements, or what a successful creation returns.

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 a single telegraphic line with no filler, so nothing is wasted, but the compression comes at the cost of clarity — it reads like an API cheat sheet rather than agent-facing guidance, and the required-field list is buried after an endpoint stub.

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, non-idempotent creation tool whose body schema is fully free-form and which has no output schema, three required field names are not enough. The description omits the scope of the body object, the confirm gate behavior, error conditions, and anything about the created record's identifier on return.

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?

This is the description's main contribution: the schema types `body` as an unconstrained object with additionalProperties {}, so the only source of required-field knowledge is the text listing asset_tag, status_id, and model_id. That materially compensates for the 50% schema coverage, though it omits optional but commonly needed fields and does not mention the `confirm` parameter.

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 names the endpoint (POST /hardware) and the title says "Create hardware," so the operation is inferable. However, it never states in its own words that it creates a hardware asset, and it does not distinguish itself from the near-duplicate sibling snipeit_gen_hardware_create or from snipeit_raw_request.

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 tool versus snipeit_gen_hardware_create or snipeit_raw_request, and no mention of prerequisites such as valid status_id/model_id values or the SNIPEIT_CONFIRM_WRITES gate. The agent must infer usage entirely.

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