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

The description discloses key behavioral traits beyond the minimal annotations: invoke runs tools even when not installed (one-off, without bloat), returns connect/checkout links under certain conditions, and requires workspace owner/admin for writes. It also mentions how search/describe flag installation state. This provides the agent with essential operation knowledge.

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 a dense single paragraph, but it is front-loaded with the main purpose and every sentence contributes unique operational detail. Given the tool's complexity (multiple actions, edge cases), the length is justified, though structured bullets or sections would improve readability.

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 complex tool with no output schema, the description covers the main actions and their flow, including edge cases like auth requirements and empty wallet retry. It explains what describe returns (full MCP profile) and what get_prompt returns (filled prompt text). Some action-specific outputs are not detailed, but the core usage scenarios are well covered.

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?

Despite the schema having 23 parameters and zero description coverage in the schema itself, the description effectively explains many key parameters (action, mcp_id, tool_id, arguments, prompt_vars, etc.) through the workflow. However, several parameters such as immediate, conversation, and tier_slug remain unexplained, so it is not a complete parameter reference.

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 and the way to run MCPs, covering search, describe, invoke, install, and prompt library functions. It distinguishes itself from siblings by explicitly outlining the core flow and scope, making it unambiguous what this tool is for.

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?

The description provides explicit guidance on when to use invoke vs install ('use install only to make an MCP PERMANENT... prefer invoke for a single/occasional use'), when to use list_tools, and what to do when credentials are missing or wallet is empty (connect link, checkout link). It also notes that writes require workspace owner/admin.

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