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

The description discloses many behaviors beyond what annotations provide: invoke works for uninstalled MCPs, returns connect/checkout links for credential/payment gaps, requires admin for writes, and flags installed_in_toolkit vs installed_in_workspace. This is rich context not visible in the sparse 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 a long, dense paragraph (400+ words) covering many sub-actions and context. It is front-loaded with the main purpose, but the structure could be improved with bullets or section breaks. Each sentence adds value, but the overall size is not concise.

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?

The description is remarkably comprehensive for a complex tool with no output schema, covering the core flow, payment/auth fallbacks, permissions, and the prompt library. It does not explain every action (e.g., resume, immediate) or return values, but provides enough for most use 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?

With 0% schema coverage, the description compensates by explaining key parameters (action, mcp_id, tool_id, arguments) through the core flow. However, many parameters (limit, query, prompt_*, immediate, tier_slug) are not individually described, leaving gaps for less common actions.

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, serving as both a catalog and execution layer for MCPs. It details the core flow (search → describe → invoke) and distinguishes itself from sibling tools like authenticate or toolkit_info.

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 is given for when to use each action: search for discovery, describe for profiles, invoke for one-off execution, install for permanent additions, list_tools for currently callable tools. It also notes prerequisites like workspace owner/admin for writes and differentiates between MCP and prompt library usage.

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