mcp-resonance

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'generate a text visualization' implies a read-only output operation, it doesn't specify whether this is computationally intensive, has rate limits, requires specific permissions, or what format the visualization takes (e.g., ASCII art, structured text). For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 that directly states the tool's purpose without unnecessary words. It's front-loaded with the core action ('generate') and resource ('text visualization'), making it immediately understandable. Every word earns its place.

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 tool has no parameters and no output schema, the description is minimally adequate. It explains what the tool produces (a text visualization about coupling), but doesn't detail the visualization format, data sources, or behavioral constraints. For a tool in a server with many sibling analysis tools, more context about its specific role would be helpful.

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 tool has zero parameters (schema coverage 100%), so there are no parameters to document. The description appropriately doesn't waste space discussing nonexistent inputs. This meets the baseline expectation for parameterless tools, though it doesn't add extra value beyond the schema's empty properties.

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 tool's purpose: 'Generate a text visualization of how MCPs and concepts are coupled together.' It specifies the verb ('generate'), resource ('text visualization'), and scope ('how MCPs and concepts are coupled together'). However, it doesn't explicitly differentiate from sibling tools like 'harmony_metrics' or 'detect_emergent_patterns' that might also involve coupling analysis.

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 doesn't mention prerequisites, appropriate contexts, or exclusions. With sibling tools like 'harmony_metrics' and 'detect_emergent_patterns' that might overlap in analyzing system relationships, the lack of differentiation leaves the agent without clear usage criteria.

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