spoolman_list_spools

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It mentions listing/searching and filter options, but omits pagination behavior, default sort, archived-spool handling (beyond the schema's allow_archived hint), and response format. This is a notable gap for a list tool with 11 parameters.

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 a single, front-loaded sentence with no filler or redundant information. It states the action and key filterable facets, earning its place.

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?

With 11 optional parameters and no output schema, the tool is moderately complex. The schema covers parameter semantics, but the description lacks return-value context, pagination defaults, and suppression of archived spools, making it minimally viable rather than complete.

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. The description adds a high-level grouping of filterable fields ('filament, vendor, material, location, lot number') but does not add syntax or format details beyond the schema, which already documents each parameter individually.

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 the specific verb 'List and search' with the resource 'spools in Spoolman', and enumerates filter dimensions (filament, vendor, material, location, lot number), making it clearly distinguishable from sibling tools like spoolman_get_spool (singular retrieval) or spoolman_create_spool (creation).

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?

The description implies usage for listing/searching spools with filters, which is clear context. However, it does not explicitly contrast with spoolman_get_spool for single-spool retrieval or state when not to use this tool, so it stops short of a 5.

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