SpecBridge MCP

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 mentions caching behavior ('Bypass in-memory cache when true' is implied through the forceRefresh parameter context) and the tool's role in system recovery, but lacks details on permissions, rate limits, error handling, or what 'load or refresh' actually entails operationally.

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 perfectly concise with two sentences that each earn their place: the first states the core functionality, the second provides crucial usage guidance. It's front-loaded with the essential action and wastes no words.

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 no annotations and no output schema, the description provides adequate context for a tool with 3 parameters and 100% schema coverage. It explains the tool's purpose and when to use it, but doesn't address what happens after loading (e.g., how other tools are affected) or potential side effects, which would be helpful given the system-impacting nature suggested by the description.

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%, so the schema already fully documents all three parameters. The description adds no additional parameter semantics beyond what's in the schema descriptions (backendId from list_backends, optional URL override, cache bypass). 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 clearly states the specific action ('Load or refresh') and resource ('OpenAPI spec from a URL'), distinguishing it from sibling tools like list_backends or get_endpoint_contract. It explicitly mentions the primary use case for initialization or recovery when 'tools fail because docs path changed'.

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 explicit guidance on when to use this tool ('Use this first if tools fail because docs path changed'), establishing it as an initialization or recovery step. It implies alternatives by referencing potential tool failures, though it doesn't name specific sibling tools as direct alternatives.

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