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

Despite weak annotations (all generic false/true), the description discloses critical behavior: invoke runs tools one-off without installing, writes require workspace owner/admin, connect/checkout link handling and retry, installed_in_toolkit vs installed_in_workspace flags, and the prompt library's public-link behavior. No contradiction 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 long (~250 words) but each sentence is information-dense and the structure moves logically from core flow to key invoke behavior, then to install, billing, and prompt library. It could be slightly more streamlined but is appropriate for a complex multi-action tool.

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 complexity (14+ actions, 23 params, sub-features like prompt library), the description covers the main flows, edge cases (auth, payment, permissions), and distinctions (permanent vs one-off). There is no output schema, so return values need not be described. It is sufficiently complete for an agent to select and invoke the correct action.

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 schema has 0% description coverage across 23 params, so the description compensates by explaining the action enum in prose and the essential parameters (mcp_id, tool_id, arguments, action values). However, not all params (e.g., limit, query, immediate, cancel_reason, prompt_vars) are explicitly mapped to their meaning, leaving some inference needed.

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 the way to run MCPs, with a specific core flow (search → describe → invoke). It distinguishes itself from siblings like report_bug and show_version by outlining the catalog, invocation, and prompt library functions.

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?

Explicit guidance throughout: 'prefer invoke for a single/occasional use', 'Use install only to make an MCP PERMANENT', 'If the MCP needs a credential/login, invoke returns a connect link; if paid and wallet empty, invoke returns a checkout link... retry'. Also designates when to use list_tools, request_mcp, subscribe/cancel, and prompt library actions.

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