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

Goes far beyond the annotations: explains that invoke runs tools even when not installed, does not bloat the tool list, returns connect/checkout links when credentials or payment are missing, and requires admin for writes. The description aligns with readOnlyHint=false and openWorldHint=true, with no contradiction to 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 long but every sentence adds value for a 14-action, 23-parameter dispatcher. It is front-loaded with purpose and core flow before diving into invoke/install distinctions and prompt library. A bulleted structure and grouping of related actions would improve scannability, but the density is justified.

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, no output schema, and zero schema descriptions, the description covers the primary flows, auth, billing, and the prompt library well. It lacks explicit return-value details for most actions and does not enumerate required params per action, which an agent would still need to discover or infer for edge cases.

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 coverage is 0%, so the description carries nearly the whole burden. It explains the most important parameter, 'action', and connects 'mcp_id', 'tool_id', and 'arguments' to the search/describe/invoke flow. However, several params like cancel_reason, prompt_vars, prompt_targets, request_details, and report_context are left for the agent to infer from their names.

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 states a clear verb ('run', 'discover', 'install') and resource ('mcp.ai marketplace', 'catalog of every MCP/tool'). It distinguishes itself from sibling calculators and support tools by defining its core flow: search → describe → invoke. It also explains the prompt-library sub-domain, leaving no ambiguity about what the tool does.

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?

Gives explicit routing guidance: prefer invoke for one-off use, use install only to make an MCP permanent; use search_prompts/get_prompt/publish_prompt for prompt text. It states prerequisites such as 'writes require workspace owner/admin' and explains when invoke returns a connect or checkout link and to retry after the user opens it.

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