List Assets (Snipe-IT)

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, destructiveHint=false. Description adds value by specifying response shape ({total, rows}) and pagination via limit/offset, plus the behavior of the 'due' parameter. No contradictions.

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?

Three sentences packing essential info: purpose, filter list, special parameter, and response format. Could be more structured with bullet points, but still clear and 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 list tool with 16 parameters and no output schema, description covers key aspects: filters, special behavior (due), response shape, and pagination. Mentions limit/offset but not typical pagination handling like total counts. Good but not exhaustive.

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 has 16 parameters with only 6% description coverage. Description groups filters (search, status IDs, etc.) but does not explain each parameter in detail. Some compensation, but lacks depth for parameters like assignedType or orderNumber.

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 specific verb 'Search/list' with clear resource 'hardware assets'. It distinguishes from siblings like snipeit_get_asset (single asset) and snipeit_list_entities (other entities) by focusing on asset listing and filtering.

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?

Provides clear context for when to use: searching and listing assets with various filters. Mentions special use case for 'due' parameter. Does not explicitly state when not to use or compare to alternatives, but siblings list helps differentiate.

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