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 burden of disclosure. It implies a read-only operation via 'Get' but fails to describe what data is returned (especially critical given no output schema exists), caching behavior, or whether the endpoint must exist (error behavior).

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 terse at three words with no wasted verbiage, but the brevity crosses into under-specification. Front-loaded with the action verb, though lacks supporting context that would justify a longer description.

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?

Incomplete for a retrieval tool with no output schema. The description fails to compensate by describing the returned data structure or content (e.g., configuration, status, metadata), leaving agents uncertain about what 'details' actually contain.

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?

Input schema has 100% description coverage ('Endpoint UUID' and 'Instance name'), so the baseline is 3. The description adds no additional semantic context about the relationship between 'uuid' and 'instance' or validation formats.

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 endpoint details' is largely tautological, merely restating the tool name with spaces and adding the vague noun 'details'. It fails to distinguish this tool from the sibling tool 'list_endpoints' or clarify what constitutes an 'endpoint' in this system.

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 provided on when to use this tool versus 'list_endpoints' for discovery, or prerequisites like needing a valid UUID beforehand. No mention of when the optional 'instance' parameter should be supplied.

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