Hyperfabric MCP Server

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

With no annotations provided, the description carries full burden but only mentions syntax, not behavioral traits. It doesn't disclose whether this is a mutation (likely, given 'Add'), what permissions are needed, if it's idempotent, or how errors are handled. For a tool that modifies fabric connections, this is a significant gap in transparency.

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 brief and front-loaded with the core purpose, followed by a syntax example. Both sentences are relevant, with no wasted words, making it efficient. However, the example could be clearer (e.g., using proper JSON syntax) to enhance usability.

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?

Given the complexity of adding fabric connections, no annotations, and no output schema, the description is incomplete. It lacks details on behavior, error handling, and return values, leaving the agent with insufficient context to use the tool effectively in a real-world scenario.

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%, so parameters are well-documented in the schema itself. The description adds minimal value by referencing 'required fields' but doesn't explain parameter meanings beyond what the schema provides. Baseline 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 ('Add') and resource ('one or more connections'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'fabricsSetFabricConnections' or 'fabricsDeleteFabricConnections', which would require specifying this is for adding new connections rather than replacing or removing them.

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 basic syntax guidance ('pass the required fields as direct arguments') but offers no context on when to use this tool versus alternatives like 'fabricsSetFabricConnections' or prerequisites such as needing an existing fabric. Without explicit when/when-not guidance, the agent lacks clear direction.

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