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

The description goes well beyond the sparse annotations (readOnlyHint false, openWorldHint true). It discloses that invoke runs tools even when not installed, returns connect/checkout links based on credentials/wallet, requires workspace owner/admin for writes, and prevents toolkit bloating. These behavioral traits are not in the 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 information-rich, covering marketplace flow, prompt library, permissions, and edge cases without wasted words. However, it is a single run-on paragraph; breaking it into structured sections would improve readability. Still, every sentence earns its place.

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 high complexity (23 params, multiple action modes, no output schema), the description covers main workflows, permission requirements, conditional invoke behaviors, and the separate prompt library. It omits specific return formats and some parameter details, but is remarkably complete for the core actions.

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 has 23 parameters with 0% coverage. The description explains the meaning of key parameters through the action flow (action, mcp_id, tool_id, arguments, prompt_*), but leaves many parameters undefined (limit, query, immediate, request_*, cancel_reason, report_context, etc.). It partially compensates but is not exhaustive.

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 covering discovery, description, invocation, and installation of MCPs/tools, plus a prompt library. It uses a specific verb+resource and enumerates the core flow (search → describe → invoke), distinguishing from sibling tools like report_bug, connect, and authenticate.

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?

It provides explicit when-to-use guidance: 'Use install only to make an MCP PERMANENT in the active toolkit... prefer invoke for a single/occasional use.' It also contrasts list_tools ('what is callable right now') and explains conditional invoke behavior with connect/checkout links. This is clear decision support.

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