assign_fabric

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

No annotations are provided, so the description carries the full burden. It implies the fabric must exist but does not disclose what happens if indices are invalid, whether the assignment is reversible, or what the return value indicates. The tool has an output schema, but the description does not mention it.

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 sentence, which is concise and front-loaded. However, it is too brief to be fully informative, lacking elaboration on parameters or behavior.

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 the lack of annotations, zero schema description coverage, and the presence of an output schema, the description should provide more context about the operation's effects, constraints, and return value. It currently only states the basic purpose, which is insufficient for safe and correct usage.

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 has 0% description coverage; neither fabric_index nor pattern_index are explained in the description. The parameter names suggest indexing into existing lists, but the description adds no explanation of their roles or expected ranges.

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 explicitly states the tool's action: assign an existing fabric to a pattern piece. It uses a specific verb ('assign') and resource ('fabric', 'pattern piece'), and distinguishes itself from sibling tools like add_fabric (which likely creates a new fabric) and set_fabric_color (which modifies color).

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 guidance on when to use this tool versus alternatives, such as add_fabric or set_fabric_color. No prerequisites or context for when assignment is appropriate are provided.

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