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

Goes far beyond minimal annotations, explaining nuanced behaviors: invoke runs tools even when not installed, returns connect/checkout links for missing credentials or empty wallets, and does not bloat the toolkit. It also discloses authorization requirements for writes and distinguishes permanent vs. one-off installations. No contradiction with 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 but well-structured, starting with the overall purpose, then the core flow, key behavioral notes, permissions, and the prompt library subsection. Each sentence adds value, though it is long—justified by the tool's complexity.

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, 14 actions, additional prompt library), the description is remarkably complete. It covers all action categories, edge cases like uninstalled MCPs and payment/auth failures, permission requirements, and the distinct prompt library feature. It even notes output details like installed_in_toolkit flags, making it sufficient despite no output schema.

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 description coverage, the description compensates by explaining the action parameter and its possible values, and referencing key parameters like mcp_id, tool_id, and arguments within the flow. However, many individual parameters (e.g., limit, cancel_reason, prompt_vars) are not explicitly described, so it doesn't fully cover all 23 parameters.

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 marketplace for MCPs/tools, functioning as both catalog and execution platform. It differentiates from sibling tools by explicitly stating its scope ('every MCP/tool, AND the way to run them') and detailing the core flow of search/describe/invoke/install.

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?

Provides explicit guidance on when to use each action: search to discover, describe to inspect, invoke for one-off runs, install for permanent additions, list_tools for current callable tools, request_mcp for unmet needs. It also states preferences (prefer invoke over install for occasional use) and alternatives, making tool selection unambiguous.

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