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

The description goes well beyond the annotations: it discloses that invoke runs tools one-off without installing, install makes permanent, writes require owner/admin, invoke returns connect/checkout links, and it explains billing, prompt-library behavior, and installed-in-toolkit vs workspace flags. No contradiction with the provided 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 a dense single paragraph but logically organized around the core flow (search → describe → invoke) and then extended to install, billing, and prompts. Every sentence contributes value, though the length and lack of formatting (e.g., bullets) make it slightly harder to scan. Appropriate for the tool's complexity.

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?

For a multi-action tool with 23 parameters and no output schema, the description covers the main flows, permission requirements, and special return behaviors (connect/checkout links). Minor gaps remain for exact return formats of search/list_tools and some action-specific parameters, but the overall picture is well-rounded.

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 compensates substantially by explaining the meaning of key parameters through the action flow: query/intent for search, mcp_id for describe, tool_id/arguments for invoke, and prompt_slug/vars for prompt functions. However, several parameters such as immediate, tier_slug, limit, cancel_reason, and report_context remain unexplained, so coverage is not exhaustive.

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, encompassing discovery, description, and execution of MCPs/tools, plus a prompt library. It uses specific verbs and an action-flow narrative, and distinguishes it from sibling tools by its unique marketplace role.

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 gives explicit guidance: 'prefer invoke for a single/occasional use' vs 'Use install only to make an MCP PERMANENT', and outlines when to use search, describe, list_tools, subscribe/cancel, report_bug, request_mcp, and prompt functions. It also specifies auth requirements and alternatives, making usage conditions very clear.

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