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

The description discloses rich behavioral context (one-off invoke without installation, owner/admin requirements, connect/checkout links requiring user action). However, it explicitly lists `uninstall` among the writes, which is a destructive operation, while the annotation `destructiveHint: false` marks the tool as non-destructive. This is a direct contradiction between description and 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 but efficient paragraph. It is front-loaded with the core purpose, uses a clear core-flow diagram (search → describe → invoke), and highlights key behaviors with 'KEY:'. Every sentence earns its place for a tool with 14 actions.

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 full lifecycle: discovery, execution, installation, billing, admin permissions, and the prompt library. It does not explain return values for most actions, but with no output schema and 23 parameters, the description is quite complete. The contradiction between the description and destructiveHint slightly undermines the overall completeness.

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 by explaining key parameter semantics through the workflow: `action` values are enumerated, and `mcp_id`, `tool_id`, `arguments`, `query`, `limit`, and `prompt_vars` are contextualized. However, not all 23 parameters are explicitly mapped; many are left to inference from their names, leaving some gaps for the agent.

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 marketplace as the official catalog and execution layer for MCPs, with a concrete core flow (search → describe → invoke) and additional responsibilities (install, billing, prompt library). It distinguishes itself from sibling tools by defining its own scope, even though action names like report_bug overlap with sibling tools.

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 clarifies list_tools for current callable tools. It also explains when to use subscribe/cancel, request_mcp, and the prompt library, giving clear decision context.

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