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

Reveals that invoke runs tools one-off without installation, that install makes permanent, that write actions require workspace owner/admin, and that auth/payment gaps return connect/checkout links. These behaviors go far beyond the sparse annotations and add critical context.

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 each section earns its place, covering the action flow, invoke vs install, auth/wallet handling, permissions, and the prompt library. It uses clear 'Core flow' and 'KEY' markers, though it could benefit from bullet-point formatting for the 14 actions.

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 tool this complex (14 actions, 23 params, no output schema), the description covers the central use cases, edge cases, and permission model well. Missing details on some actions (resume, request_mcp) and parameters prevent a perfect score.

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?

The description explains key parameters through the workflow (query, mcp_id, tool_id, arguments, prompt_* fields) but leaves many schema fields (limit, request_details, report_context, cancel_reason) unspecified. Given 0% schema coverage, it substantially compensates but not exhaustively.

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?

Clearly identifies the marketplace as the catalog and execution layer for MCPs, with an explicit search→describe→invoke flow. Distinguishes itself from sibling tools by covering discovery, running, installation, billing, and the prompt library.

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?

Explicitly states the core flow, when to prefer invoke over install, how to handle connect/checkout links, and what list_tools/subscribe/cancel/report_bug/request_mcp do. This gives clear directives for agent decision-making.

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