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

The description transparently explains the tool's behavior: it returns the created MCP with its id, does not create an ingest key, and cannot mint keys. This goes beyond a simple 'creates a resource' statement and sets accurate expectations about the result and limitations.

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 two concise sentences that deliver essential information without redundancy. It is well-structured and easy to parse.

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?

The description covers the input, the return value (MCP with id), and a key caveat (no ingest key, dashboard directions). This provides sufficient context for a user to understand the tool's purpose and limitations.

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 input schema fully describes the 'name' parameter with a clear example. The description does not add extra meaning beyond the schema, so it falls at the baseline for parameter coverage.

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 verb 'Add' clearly specifies creating a new MCP server, and the description distinguishes it from sibling tools like list_mcps, get_mcp, rename_mcp, and delete_mcp. The purpose is unambiguous.

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 offers practical guidance by noting that no ingest key is created and directing the user to the dashboard for key generation. It lacks an explicit mention of when to use this tool versus alternatives, but the function is distinct enough that the context is clear.

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