Hyperfabric MCP Server

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

No annotations are provided, so the description carries the full burden. It states a read operation ('Get'), implying it's non-destructive, but fails to disclose critical behavioral traits like authentication needs, rate limits, pagination, or response format. For a security-related tool with zero annotation coverage, this 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 no wasted words. It's front-loaded and clear, though it could benefit from slightly more detail given the lack of annotations and sibling tool context.

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 authentication tools, no annotations, no output schema, and rich sibling tools, the description is incomplete. It doesn't explain return values, error conditions, or how it fits into the broader auth workflow, leaving the agent under-informed for secure operations.

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 the single parameter 'includeMetadata' fully documented in the schema. The description adds no additional meaning beyond what the schema provides, such as examples of metadata or implications of including it. Baseline 3 is appropriate when 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 'Get the list of bearer tokens' clearly states the verb ('Get') and resource ('bearer tokens'), but it's vague about scope and lacks differentiation from sibling tools like 'authGetBearerToken' (singular) or 'authCreateBearerTokens'. It doesn't specify whether this retrieves all tokens, active tokens, or tokens for a specific context.

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 like 'authGetBearerToken' (singular) or 'authCreateBearerTokens'. The description offers no context about prerequisites, such as authentication requirements, or exclusions, leaving the agent to infer usage based on tool names alone.

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