MetaMCP Admin MCP

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

No annotations are present, so the description carries full disclosure burden. It states 'Delete' implying mutation, but provides no details about permanence, cascade effects on dependent resources, required permissions, or success/failure behaviors.

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?

While brief, this is under-specification rather than effective conciseness. Two words fail to earn their place for a destructive operation requiring safety context and behavioral constraints.

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 destructive mutation tool with no annotations and no output schema. Fails to explain what happens to the deleted endpoint, whether references are cleared, or how to verify deletion success.

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 (both 'uuid' and 'instance' are documented in the schema). Since schema coverage is high, baseline is 3. The description adds no semantic clarification beyond the schema.

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 'Delete an endpoint' is tautological, essentially restating the tool name 'delete_endpoint' with articles. It fails to distinguish from sibling deletion tools (delete_server, delete_namespace, delete_api_key) or clarify what type of endpoint this refers to.

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 usage guidance provided. The description does not indicate prerequisites (e.g., verifying endpoint existence), when to use versus other operations, warning about irreversibility, or relationships to create_endpoint or get_endpoint.

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