delete_fabric

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It only says 'Delete', which implies mutating and destructive behavior, but it does not disclose whether deletion is irreversible, whether assigned fabrics are affected, or whether undo/checkpoint behavior applies.

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 crisp sentence with no filler words. It is concise and front-loaded, though it is arguably too sparse for a destructive operation, which slightly limits the appropriateness of its size.

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 tool with no annotations and no output schema, the description is incomplete. It omits critical context about the fabric_index meaning, side effects, reversibility, and how this operation interacts with patterns or project state.

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 description coverage is 0% and the description adds no meaning to fabric_index. It does not explain where the index comes from, whether it is zero-based, or how it relates to get_fabric_list, so the agent has insufficient parameter semantics.

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 ('Delete'), a clear resource ('fabric'), and scope ('from the project'). This distinguishes it from sibling operations like delete_pattern, add_fabric, replace_fabric, and export_fabric, so an agent can tell what tool this is without inspecting schemas.

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 guidance is given for when to use this tool versus alternatives such as replace_fabric or delete_pattern. There are no prerequisites, exclusions, or context about when deletion is appropriate, leaving the agent to infer usage.

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