fabricsDeleteFabric

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

No annotations are provided, so the description carries full burden for behavioral disclosure. While 'Delete' implies a destructive mutation, the description fails to specify whether this action is reversible, what permissions are required, whether it affects connected resources, or what happens on success/failure. For a destructive tool with zero annotation coverage, this lack of behavioral detail is a significant gap.

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, efficient sentence with zero wasted words. It's front-loaded with the core action and target, making it immediately understandable. Every word earns its place, achieving optimal conciseness for a simple tool.

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 destructive mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't address critical context like what 'delete' entails (soft/hard deletion), error conditions, side effects on related entities, or response format. The combination of high-risk operation and lack of structured metadata requires more descriptive guidance than provided.

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 input schema has 100% description coverage, with the single parameter 'fabricId' documented as 'The fabric id or name.' The description doesn't add any meaningful semantic context beyond this, such as format examples or validation rules. With complete schema coverage, the baseline score of 3 is appropriate as the schema does the heavy lifting.

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 clearly states the action ('Delete') and target ('a specific fabric'), which is a specific verb+resource combination. It distinguishes from sibling tools like 'fabricsUpdateFabric' or 'fabricsGetFabric' by specifying deletion rather than modification or retrieval. However, it doesn't explicitly differentiate from other deletion tools like 'fabricsDeleteFabricConnection' or 'fabricsDeleteFabricConnections'.

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 guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., whether the fabric must be empty or inactive), consequences of deletion, or when to choose this over other fabric-related tools like 'fabricsUpdateFabric' for deactivation. The absence of usage context leaves the agent without operational guidance.

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