MetaMCP Admin MCP

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

With no annotations provided, the description carries the full disclosure burden. It clearly states the core operation but lacks critical behavioral context: it does not specify the output format, what constitutes success/failure, whether checks are read-only (implied but not confirmed), timeout behavior, or if failed checks throw exceptions versus return error objects.

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 single sentence is front-loaded with the action and contains zero wasted words. Every term ('Check', 'connectivity', 'all configured MetaMCP instances') conveys essential operational scope without redundancy.

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's low complexity (zero parameters, no mutations) and clear purpose, the description is nearly sufficient. However, lacking an output schema, it should ideally describe what health status information is returned to make the tool fully actionable.

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?

With zero parameters, the baseline score is 4 per evaluation rules. The description appropriately makes no mention of parameters since none exist, and the empty schema requires no semantic elaboration.

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 'Check connectivity to all configured MetaMCP instances' provides a specific verb (Check), clear resource (connectivity), and precise scope (all configured MetaMCP instances). It effectively distinguishes this diagnostic tool from sibling CRUD operations like create_server or list_instances.

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?

While the purpose implies this is for monitoring/diagnostic scenarios, the description provides no explicit guidance on when to prefer this over list_instances for status checking, nor does it mention prerequisites or conditions for use.

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