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

Annotations are limited to hints, so the description carries the burden. It discloses that invoke runs one-off without installing, returns connect/checkout links for auth/payment, requires owner/admin for writes, and explains the prompt library's link behavior (opens without login). 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 long but organized with a clear progression: definition, capabilities, core flow, key behaviors, alternatives, permission requirements, and prompt library. Every sentence contributes meaning, though it could be tightened.

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?

Covers the major actions, edge cases (auth/payment), permission model, and the prompt library. However, it omits mention of the 'resume' action and the effects of uninstall beyond permission requirements, leaving a few gaps for a 23-parameter multi-action tool.

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 description coverage is 0% for 23 parameters. The description explains the action/tool_id/query flow and mentions prompt-related fields implicitly, but many parameters (tier_slug, immediate, conversation, report_context, prompt_targets) are not explained. It provides partial compensation but not enough for a parameter-heavy tool.

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 defines the marketplace as the in-platform catalog of every MCP/tool and the way to run them. It explicitly outlines the core flow (search → describe → invoke) and distinguishes from sibling tools by covering capability requests 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?

Explicit guidance distinguishes invoke vs install: 'prefer invoke for a single/occasional use' vs 'Use install only to make an MCP PERMANENT'. It also explains when to use list_tools, subscribe/cancel, report_bug, and request_mcp, and how to handle connect/checkout flows before retrying.

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