MetaMCP Admin MCP

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

With zero annotations provided, the description carries the full burden of behavioral disclosure but fails to deliver. It does not disclose whether this operation overwrites existing configs on the target, generates new UUIDs, validates config compatibility between instances, or handles errors if the source server doesn't exist. 'Copy' implies non-destructive read on source, but target-side behavior (idempotency, upsert vs. fail-on-conflict) is unspecified.

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?

Extremely concise at nine words in a single sentence. Front-loaded with the action verb 'Copy'. While efficient, it may be overly terse given the complexity of cross-instance operations; the single sentence earns its place but leaves substantial contextual gaps that additional sentences should cover.

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?

Inadequate for a mutation tool performing cross-instance operations with no output schema and no annotations. Missing essential context: conflict resolution behavior (clobber vs. fail), whether the operation is synchronous or async, return value structure (new ID? success boolean?), and validation rules. For a tool with sibling 'create_server', it should clarify if this is essentially 'create from template' semantics.

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 coverage is 100% with clear parameter descriptions already provided in the input schema. The tool description loosely reinforces the 'from one to another' relationship between sourceInstance and targetInstance, but adds no additional semantics regarding valid instance name formats, whether instances must be in the same cluster, or constraints on serverUuid format beyond what the schema already states.

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?

States a specific verb (Copy) and resource (MCP server config) with clear scope (from one instance to another). However, it does not explicitly differentiate from sibling 'create_server' (which creates new configs versus copying existing ones), leaving some ambiguity for agents choosing between instantiation methods.

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?

Provides no guidance on when to use this tool versus alternatives like 'create_server' or 'update_server'. Missing critical prerequisites such as whether the target instance must exist beforehand, connectivity requirements between instances, or permissions needed for cross-instance operations.

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