spoolman_list_filaments

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

With no annotations, the description carries the burden of behavioral disclosure. It explains filtering support but does not explicitly state that the operation is read-only or describe pagination behavior (e.g., limit/offset semantics). The 'and more' is vague, leaving some behaviors undisclosed.

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 concise and front-loaded with the core purpose. The second clause is slightly vague ('and more') but not wasteful. It could be more precise, but it remains 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?

Given a 10-parameter tool with no output schema, the description is minimal. It does not explain default behavior (e.g., returns all filaments if no filters) or confirm that results are paginated, though limit/offset parameters imply it. This leaves some gaps for a complex tool.

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?

The schema already documents all 10 parameters with descriptions (100% coverage), so the baseline is 3. The description's mention of filters (vendor, material, color, article number) adds no meaning beyond what the schema provides, and 'and more' adds no specific value.

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 clearly states the action ('List and search') and the resource ('filaments in Spoolman'), distinguishing it from sibling tools like list_spools and list_vendors. It also mentions filtering capabilities, making the purpose unambiguous.

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 provides clear context for when to use the tool: listing/searching filaments. However, it does not explicitly exclude alternatives (e.g., get_filament for a single filament) or mention when not to use it, so it falls 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.