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

Annotations are minimal (readOnlyHint=false, destructiveHint=false, openWorldHint=true, idempotentHint=false), so the description carries the behavioral burden and does so excellently. It discloses that invoke runs tools even when MCPs are not installed, returns connect links for credential needs and checkout links for payment, and requires owner/admin for writes. No contradiction with annotations; description adds rich context.

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 dense and front-loaded with purpose and flow, but it is quite long (over 200 words). It includes some repetition, such as 'pontualmente (one-off)' and 'prefer invoke for a single/occasional use,' which could be tightened. Nevertheless, the length is justified by the tool's complexity and the need to explain multiple action types and the prompt library.

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 (23 params, 14 actions, no output schema), the description is remarkably complete. It covers the entire workflow, mentions error-handling scenarios (connect link, checkout link), permission guards for writes, and the separate prompt library with its own sub-actions. It addresses all major use cases an agent would face, making it self-sufficient for correct invocation.

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?

Schema description coverage is 0%, so the description must compensate. It effectively explains the core parameters (action, mcp_id, tool_id, arguments) and their roles in the flow, and covers prompt-related params (prompt_slug, prompt_vars, etc.) contextually. However, some parameters like limit, query, immediate, and tier_slug are not explicitly described, though their purpose is inferable. The description provides strong semantic grounding for the most important parameters, but does not exhaustively document all 23.

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 states it is the official marketplace and catalog for MCPs/tools, with a verb+resource structure. It thoroughly distinguishes itself from sibling tools by explaining its role as the central discovery and execution mechanism, and explicitly covers capability requests like 'find an MCP that does X' and 'is there a tool for Y'.

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?

Provides explicit, actionable guidance: core flow (search → describe → invoke) with clear when-to-use for invoke vs install, and when to use list_tools, subscribe/cancel, report_bug, and request_mcp. It also explains permission requirements for write actions and the prompt library path, giving both inclusion and exclusion criteria.

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