Hyperfabric MCP Server

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. It only states the action ('Get the list') without detailing response format (e.g., list structure, pagination), error conditions, authentication requirements, rate limits, or whether it's read-only (implied but not explicit). This is inadequate for a tool with potential complexity in networking contexts.

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, direct sentence with zero wasted words. It's front-loaded with the core action and resource, making it highly efficient and easy to parse, though this conciseness comes at the cost of detail in other dimensions.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what VNIs are, how the list is structured, or any behavioral traits (e.g., read-only nature, potential errors). For a networking tool with 3 parameters and no structured safety hints, more context is needed to guide effective use.

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 100%, with clear descriptions for all parameters (fabricId, candidate, includeMetadata). The description adds no additional meaning beyond the schema, such as explaining relationships between parameters or typical use cases. Baseline 3 is appropriate since the schema does the heavy lifting, but no extra value is provided.

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 'Get the list of VNIs' clearly states the verb ('Get') and resource ('VNIs'), making the basic purpose understandable. However, it lacks specificity about what VNIs are (Virtual Network Identifiers) or how they relate to the fabric context, and it doesn't differentiate from sibling tools like 'vnisGetFabricVni' (singular) or 'vnisGetFabricVniMembers', leaving ambiguity about scope.

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 provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing a valid fabric), exclusions, or comparisons to sibling tools like 'vnisGetFabricVni' (for a single VNI) or 'vnisGetFabricVniMembers', leaving the agent to infer usage from context alone.

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