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

The description goes far beyond the sparse annotations by detailing key behaviors: invoke works even for uninstalled MCPs, returns connect/checkout links for auth/payment, performs a one-off install without bloating the toolkit, and flags installed status in search/describe. It also discloses that writes require workspace owner/admin. No contradictions with annotations.

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 information-dense with no fluff, but it is a single unbroken block of text that is lengthy and lacks clear structure. The 'KEY:' marker and a few commas help, but the overwhelming amount of detail makes it harder to parse than it could be.

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 main flows, auth/payment edge cases, permission requirements, and the prompt library. However, it omits some actions (e.g., resume) and does not explain what certain parameters do, leaving gaps for an agent trying to fully understand the tool's capabilities. Still, given the tool's complexity, it is largely complete.

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 0% schema description coverage, the description must compensate, and it does explain the most critical parameters: action, mcp_id, tool_id, arguments, and the prompt_* fields. However, it leaves some parameters unexplained (e.g., immediate, conversation, message, cancel_reason, request_details), so while it adds substantial meaning, it doesn't fully cover all 23 parameters.

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 clearly identifies the tool as the official mcp.ai marketplace and explains its dual role as catalog and runner of MCPs/tools. It also distinguishes itself from sibling tools by outlining its unique capabilities (search, describe, invoke, prompt library), making it highly specific and 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 provides explicit guidance on when to use each action: 'prefer invoke for a single/occasional use', 'Use install only to make an MCP PERMANENT', and 'request_mcp asks us to build a NEW MCP when nothing fits'. It also outlines the core flow (search → describe → invoke) and clarifies when to use list_tools, subscribe/cancel, and report_bug. This is exemplary usage guidance.

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