GET /hardware/{id}/files

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds nothing behavioral beyond restating the title: no pagination, no indication of what metadata each file entry carries, no note that an empty list is returned for assets without uploads.

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?

Two short sentences, the plain-language purpose first and the path second; no wasted preamble. The 'Generated from Snipe-IT OpenAPI operation hardware-list-files' clause is boilerplate provenance but is compact and does no harm.

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 list endpoint with full schema coverage and rich annotations, the description is adequate but thin. It omits any sense of the response shape (file names, sizes, URLs) and pagination behavior, which is not covered by an output schema.

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?

There is a single parameter with 100% schema coverage ('ID of the asset'), so the schema already does the work. The description's path template reinforces that the id refers to a hardware asset but adds no format or sourcing guidance beyond the schema, making 3 the correct baseline.

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 specific verb and resource, 'List uploaded files for an asset', plus the concrete path GET /hardware/{id}/files. It does not distinguish this from close siblings such as snipeit_gen_hardwareidfilesfile_id (single-file retrieval) or snipeit_gen_hardware_files_delete, leaving the agent to infer the boundary from names alone.

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 statement of when to use this versus alternatives, no prerequisite about the asset having files uploaded, and no pointer to snipeit_gen_hardware_upload_files for the write counterpart. The only implied guidance is the required asset id in the path.

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