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

The description discloses important behavioral traits beyond annotations: invoke works even when the MCP is not installed, does not bloat the tool list, returns connect/checkout links when auth/payment is needed, and writes require workspace owner/admin. It also explains the shareable prompt link behavior and installed_in_toolkit vs installed_in_workspace flags. No contradiction with annotations exists.

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 front-loaded with the main definition and core flow, then logically groups install vs invoke, permission requirements, and the prompt library. It is dense and mostly earns its length given the tool's complexity, though a bulleted or more segmented structure would improve scannability.

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 14-action, 23-parameter tool with no output schema, the description is unusually complete: it covers the main flows, auth/payment edge cases, permissions, and the prompt library. It stops short of specifying return shapes for every action and omits a few action-specific parameters, so it is not perfect, but it is far above the minimum viable level.

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 partially compensates by explaining the action enum values and the roles of mcp_id, tool_id, arguments, and prompt-related parameters in the core flow. However, many parameters like limit, immediate, cancel_reason, report_context, conversation, and prompt_targets are left undocumented, so an agent would still have to guess their exact semantics.

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 defines the tool as 'the official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them,' which clearly states its core purpose. It also distinguishes it from sibling openfinance tools by covering MCP discovery, description, and execution rather than financial data access. The search→describe→invoke core flow further specifies 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?

The description gives explicit usage guidance, e.g., 'Use install only to make an MCP PERMANENT in the active toolkit' and 'prefer invoke for a single/occasional use.' It also explains when to use request_mcp, search_prompts, and publish_prompt, and how to handle credential/checkout retries, making alternative choices within the tool very clear.

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