pattern_list

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 does disclose that detail=True adds outline line data and that line indices are what sew() uses, which is useful cross-tool context. However, it does not mention whether this is a read-only operation, performance implications of detail=True, or what the default response shape looks like beyond the field list.

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 sentences, front-loaded with the core listing behavior, then a compact explanation of the optional detail flag. Every clause earns its place, and the cross-reference to sew() is high-value context.

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 list tool with one optional boolean parameter, the description covers the main behavior and the parameter's effect. It lacks an explicit return format description, but the field list is given and no output schema exists, so the description is reasonably complete. Minor gap: no mention of whether the list is ordered or filtered.

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 coverage is 0%, so the description must compensate. It does: it explains the single parameter detail and exactly what detail=True adds (outline lines with length/location, seam groups). This is meaningful semantic value beyond the bare boolean schema.

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 states a specific verb ('List') and resource ('pattern pieces') and enumerates the fields returned (index, name, arrangement, fabric, bbox). It distinguishes itself from pattern_info by focusing on listing pieces rather than a single piece's details, though it doesn't explicitly name the sibling alternative.

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: call it to list pattern pieces, and use detail=True when you need outline lines and seam groups. It does not explicitly state when to prefer pattern_info or seams_list, nor does it give exclusions, so the guidance is present but not fully explicit.

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