assign_fabric_to_pattern

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

With no annotations provided, the description carries the behavioral disclosure burden. It does explain the three assignment modes, which is useful context beyond the tool name. However, it does not state whether assignment overwrites an existing fabric assignment, whether the operation is reversible, or what 'linked' vs 'unlinked' concretely means.

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 compact and well-structured: one clear purpose sentence followed by a tight Args block. Every sentence earns its place, and there is no filler or repetition of schema details.

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 three-parameter tool with no output schema, the description covers the essential invocation details: required indices, the optional assign_option, and what each option means. It is slightly incomplete because it does not define the linked/unlinked behavior or mention error/precondition cases, but the core call is usable.

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, but the description fully compensates by documenting all three parameters: zero-based fabric_index, zero-based pattern_index, and the assign_option 1/2/3 meanings. It adds meaningful semantics that the bare schema types and default alone do not provide.

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 operation — 'Assign a fabric to a pattern piece' — with a clear verb and resource. It is not a tautology and is understandable on its own. However, it does not explicitly distinguish itself from sibling tools such as get_fabric_for_pattern or set_fabric_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?

The description provides no explicit when-to-use or when-not-to-use guidance, and does not name alternatives. It also omits prerequisites such as the fabric and pattern piece needing to exist before assignment. The assign_option explanations are parameter semantics, not usage selection guidance.

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