List hardware (assets)

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

The annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so safety and side-effect behavior are covered elsewhere. The description adds only that the endpoint is paginated and supports search/filtering; it does not explain truncation behavior, the 10,000-row auto-pagination cap, or rate-limit implications.

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?

The description is very short and front-loaded with the endpoint and pagination fact, so it is concise. However, the extreme brevity leaves out important selection and parameter details, making it under-specified rather than perfectly efficient.

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 16-parameter listing endpoint with no output schema, the description is incomplete: it omits guidance on pagination/truncation behavior, the meaning of most filters, and how this differs from other hardware search/list tools. The annotations cover read-only safety, but the remaining operational context is insufficient.

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?

With 16 parameters and only 38% schema description coverage, the description must compensate but instead says only 'supports search and common filters.' Several filter parameters such as model_id, status_id, company_id, category_id, location_id, and manufacturer_id are undocumented in both schema and description, so an agent lacks clear semantics for most filters.

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 identifies the endpoint and general capability (GET /hardware, paginated, supports search and filters), so an agent can infer it lists hardware. However, it does not distinguish this tool from close siblings such as snipeit_search_hardware or snipeit_gen_hardware_list, leaving the agent to guess which list/search endpoint to use.

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 explicit guidance on when to use this tool instead of snipeit_search_hardware, snipeit_raw_request, or the generated hardware list tools. The mention of search and filters implies a broad list operation, but no conditions or alternatives are stated.

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