GET /hardware/byserial/{serial}

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered without description help. The description adds nothing beyond that — no note on the `deleted` inclusion flag's effect, no statement about what a miss returns, only a provenance line about OpenAPI generation. It does not contradict the annotations, but it carries no extra behavioral weight.

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 the purpose statement leads, but the second sentence ("Generated from Snipe-IT OpenAPI operation hardware-by-serial") is boilerplate that consumes half the text without informing invocation. Not padded, but not fully earning its space either.

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 simple read-only two-parameter GET, the schema plus annotations cover most needs, and there is no output schema the description would need to explain. Still, the agent gets no picture of what the response contains or how a not-found serial behaves, and the tag/serial confusion leaves a real gap.

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 baseline is 3, but the description's phrase "by asset tag" is inconsistent with the `serial` parameter, which the schema correctly describes as "The serial number (not the ID)." That mismatch risks the agent passing a tag value, so it subtracts rather than adds meaning.

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 gives a verb and resource ("Get the details of a specific asset") and the path makes the lookup key clear, but it then says "by asset tag," which contradicts the {serial} path segment and the `serial` parameter. With siblings snipeit_get_hardware_by_tag and snipeit_get_hardware_by_id in the same family, this mislabeling actively blurs the distinction the agent needs.

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 serial lookup versus asset-tag lookup, ID lookup, or the broader snipeit_search_hardware / snipeit_list_hardware tools. The only usage cue is implicit in the path. No exclusions or alternatives are named.

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