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

Beyond annotations, it discloses one-off invocation behavior, auth/checkout link fallbacks, permission requirements, and the fact that invoke works even when the MCP is not installed. No contradiction with 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 dense and packed into one long paragraph, which hampers scannability. It begins with a clear value statement but mixes in foreign-language examples and lacks bullet points or section breaks.

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 23-parameter, 14-action tool, it covers most workflows and return types (profiles, connect/checkout links, shareable prompt links). It omits explicit result shapes for search/list_tools and the resume action, so not fully complete.

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 prose explains action values and key parameters (query, mcp_id, tool_id, arguments, prompt_vars, prompt_slug). However, several params like limit, immediate, tier_slug, resume, and prompt_targets are not explicitly tied to actions, 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 clearly identifies the tool as the official mcp.ai marketplace—a catalog and execution layer for MCPs, with explicit verbs like 'discovers', 'describe', 'invoke', and 'list_tools'. It distinguishes from siblings by outlining a core flow and covering a prompt library.

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', and describes the search→describe→invoke sequence. It also states that writes require workspace owner/admin, giving clear prerequisites.

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