snipeit_hardware_list

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

With no annotations, the description carries the behavioral burden, and 'List' reasonably implies a read-only, non-destructive operation. It does not disclose response format, pagination behavior beyond the schema, or access considerations, but the core action is transparent and unlikely to mislead.

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?

One short, front-loaded sentence with no wasted words. It is concise and easy to parse, though 'with optional filters' is somewhat redundant with the schema, which prevents a 5.

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?

Given the fully documented input schema, the one-sentence description is minimally viable for making a simple list call. However, with no output schema and no annotations, it leaves the agent without guidance about result shape, when to prefer this over related hardware tools, or how the optional filters interact.

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 input schema already documents all 10 parameters with useful descriptions such as 'Search term (asset tag, serial, name)' and 'Max results (default 50)'. The description adds only the generic phrase 'optional filters', which adds no parameter-level meaning beyond the schema.

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 uses a specific verb and resource, 'List hardware assets', which clearly identifies the tool's core operation and distinguishes it from sibling tools like snipeit_hardware_get, snipeit_hardware_create, or snipeit_hardware_checkin. However, it does not explicitly contrast with any named sibling, so it does not earn a 5.

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 is provided about when to use this list endpoint versus alternatives such as snipeit_hardware_get, snipeit_hardware_by_tag, or the related list tools. The phrase 'with optional filters' is generic and does not explain selection criteria, exclusions, or expected use cases.

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