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

Annotations already indicate non-read-only and non-idempotent behavior, and the description adds substantial context: invoke runs one-off without installing, missing credentials return a connect link, unpaid paid MCPs return a checkout link, and writes require workspace owner/admin. It also discloses the prompt library's shareable link 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?

The description is long but appropriately so for a multi-action dispatcher. It is front-loaded with the core flow and KEY invoke behavior, and each section adds distinct value. It could be improved with bullet points or clearer separation between the MCP marketplace and prompt library sections.

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?

It covers the main flows, side effects, auth requirements, and several return behaviors (connect link, checkout link, shareable prompt link). However, with no output schema, it omits return shapes for search/describe, and it never mentions the 'resume' action or several action-specific parameters, leaving notable gaps for a tool of this complexity.

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 and 23 parameters, the description compensates by explaining the critical action parameter and the tool_id flow, plus prompt variables and slug concepts. However, many parameters (immediate, tier_slug, conversation, prompt_targets, report_context, request_details) remain unexplained, so it only partially bridges the gap.

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 mcp.ai marketplace and the way to run MCPs, with an explicit core flow (search → describe → invoke). It distinguishes itself from siblings by covering catalog discovery, execution, installation, billing, and prompt library actions.

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?

It gives explicit when-to-use guidance: 'prefer invoke for a single/occasional use' and 'Use install only to make an MCP PERMANENT'. It also explains when to use list_tools, request_mcp, report_bug, and the prompt library actions, providing clear alternatives.

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