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

The description goes well beyond the sparse annotations by disclosing that writes require workspace owner/admin, that invoke runs tools one-off without installing them, and that paid/credential-gated MCPs return checkout/connect links. No contradiction with readOnlyHint=false or destructiveHint=false.

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 but front-loaded with purpose and core flow, and nearly every sentence adds a distinct behavioral fact. It is long, but the 14-action/23-parameter surface area justifies the length; a bit more structure would help.

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?

It thoroughly covers the marketplace search/describe/invoke lifecycle, install-vs-invoke tradeoffs, permission requirements, and prompt library. But it omits several actions/params (resume, immediate, tier_slug, conversation, prompt_tool, cancel_reason, etc.) and there is no output schema to compensate, so it is 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 coverage, the description carries the full burden, and it does explain the central action values and the tool_id flow. However, many parameters (limit, query, immediate, tier_slug, conversation, cancel_reason, prompt_tool, prompt_targets, arguments, etc.) are never mentioned or mapped to actions, so the agent is left to infer their meaning.

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 'official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them' and then details the core search→describe→invoke flow, making the tool's role unmistakable. It does not explicitly contrast itself with sibling tools like toolkit_info or connect, so it stops short of full sibling differentiation.

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?

Explicit guidance abounds: 'prefer invoke for a single/occasional use', 'Use install only to make an MCP PERMANENT', and 'request_mcp asks us to build a NEW MCP when nothing fits.' It also explains the retry flow for connect/checkout links, which tells the agent exactly when and how to proceed.

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