fabricsAddFabrics

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Add a fabric' implies a creation/mutation operation but fails to describe critical behaviors: whether this requires specific permissions, if it's idempotent, what happens on conflicts (e.g., duplicate names), or what the response contains. The description adds minimal context beyond the basic action.

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 appropriately concise with two sentences that are front-loaded: the first states the purpose, and the second provides usage syntax. There's no unnecessary verbosity, though the second sentence could be more informative about the tool's behavior rather than just argument passing.

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 mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'adding a fabric' entails operationally, what validation occurs, what the return value looks like, or error conditions. Given the complexity implied by the detailed input schema, the description should provide more context about the tool's behavior and outcomes.

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 description coverage is 100%, providing comprehensive documentation for the single 'fabrics' parameter and its nested properties. The description adds no parameter semantics beyond what's in the schema, only mentioning how to pass arguments. With high 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 'Add a fabric' is a tautology that restates the tool name without providing meaningful context. While it specifies the verb ('Add') and resource ('fabric'), it lacks specificity about what a fabric is or what the operation entails, making it vague compared to more detailed sibling tools like 'fabricsUpdateFabric' or 'fabricsDeleteFabric'.

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 mentions how to pass arguments but offers no context about prerequisites, when this operation is appropriate, or how it differs from sibling tools like 'fabricsUpdateFabric' or 'fabricsGetFabric'. This leaves the agent without usage direction.

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