add_fabric

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

No annotations exist, so the description carries the full disclosure burden. It conveys that a new fabric is created from a file but does not mention side effects such as whether the project must be saved, whether duplicates are allowed, or what happens on file load failure.

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 two sentences, front-loaded with the primary action and followed by a terse parameter explanation. There is no filler or redundant elaboration.

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 one-parameter tool this is usable, but it omits common prerequisites (e.g., an open project, file accessibility) and any behavioral context such as duplicate handling. It is adequate but not complete, especially with no annotations or output schema to fill the gaps.

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 only provides a title 'File Path'; the description adds the crucial requirements that the path must be absolute and must point to a .zfab or .jfab file. This is meaningful semantic information for the single required parameter.

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?

States the action ('Add a new fabric') with the exact resource and input format (.zfab/.jfab). It is clear what the tool does, though it does not explicitly name sibling tools such as replace_fabric or apply_fabric_json to differentiate usage.

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?

No when-to-use guidance or alternative tool recommendations are provided. It does not explain when to choose this over replace_fabric, apply_fabric_json, or import_file, leaving the choice to inference.

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