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

The description discloses key behaviors beyond annotations: invoke runs tools even when the MCP is not installed and avoids bloating the toolkit; it returns connect or checkout links conditionally; writes require workspace owner/admin; publish_prompt returns a link that opens without login. This is rich behavioral context that the sparse annotations (readOnlyHint false, openWorldHint true) do not provide.

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 front-loaded with a clear definition and core flow. Every sentence adds context, from the one-off invoke behavior to auth requirements and the prompt library. It lacks visual structuring (e.g., bullets) but remains organized and information-dense, making it appropriately sized for a tool with 23 parameters and 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?

Given the tool's complexity and the absence of an output schema, the description explains return behaviors (connect links, checkout links, profiles, prompt links), installed flags, and permission requirements. It covers most use cases but omits details on actions like resume and uninstall, and does not mention all parameters, so it falls short of full 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?

Schema description coverage is 0%, so the description carries a heavy burden. It explains the critical parameters and their roles within the core flow (action=search/describe/invoke, mcp_id, tool_id, arguments) and implicitly covers prompt library parameters. However, it omits several parameters (limit, immediate, tier_slug, resume, prompt_targets) and does not systematically map each field, leaving gaps.

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 opens with 'The official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them,' which clearly states the tool's function as a marketplace and execution interface. It further differentiates itself from sibling tools by describing its unique role (search/describe/invoke) versus the Nuvemshop-specific or auth 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?

Provides explicit guidance: 'Use install only to make an MCP PERMANENT... prefer invoke for a single/occasional use.' It also delineates when to use search, describe, invoke, list_tools, request_mcp, and the prompt library functions. This directly addresses when to use this tool versus alternatives like install or list_tools.

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