Get hardware by id

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond them — no note on whether the record includes custom fields, relations, or what happens on a nonexistent ID. It does not contradict the annotations.

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 and front-loaded, but that brevity is under-specification rather than conciseness — the entire description is a five-token endpoint path with no explanatory content to be concise about.

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?

With no output schema, the description carries the burden of explaining what is returned, and it says nothing about the response shape. For a retrieval tool in a crowded namespace with three other hardware-lookup siblings, this leaves the agent guessing on both input identity and output.

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 0% and the single 'id' parameter has no description in the schema. The URL template "{id}" only confirms that id is a path segment; it does not say the value is the Snipe-IT internal hardware/asset primary key (as opposed to an asset tag or serial, which have their own tools).

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 is the raw endpoint string "GET /hardware/{id}", which only restates the tool name and title in URL form. It gives no indication of what a 'hardware' record is or how this differs from siblings like snipeit_get_hardware_by_tag, snipeit_get_hardware_by_serial, or snipeit_list_hardware.

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 the many alternatives in the sibling list (fetch by tag, by serial, list, search). The agent must infer that this is the numeric-ID lookup variant purely from the tool name.

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