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

The disclosure goes well beyond annotations: it states that writes require admin, invoke runs tools one-off without installing, and credential/payment failures produce actionable links. These behavioral insights are critical for an agent to anticipate side effects and user interactions.

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 lengthy, dense paragraph that mixes MCP operations, billing, auth, and prompt library. It front-loads the main purpose but could benefit from bullet points or segmentation. The length is justified by complexity, but readability suffers.

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 14 actions and 23 parameters, the description is remarkably complete: it covers the discover-run-install lifecycle, prompt library, admin prerequisites, and failure-handling behaviors. It doesn't enumerate every return structure, but for a tool of this complexity, the coverage is solid.

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 carries the burden of explaining the key action parameter and the purpose of tool_id/arguments. It covers the main actions but leaves many parameters (tier_slug, immediate, prompt_targets, conversation) without explicit explanation. Still, the core flow demystifies the most important 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 explicitly defines the tool as 'the official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them.' It outlines the core flow (search → describe → invoke) and covers the prompt library, making the tool's role unmistakable even among siblings.

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 clear usage directives like 'prefer invoke for a single/occasional use' and 'Use install only to make an MCP PERMANENT.' It explains when invoke returns connect/checkout links and distinguishes list_tools from the discovery flow. However, it doesn't explicitly contrast with sibling tools like connect/authenticate, so a 5 isn't warranted.

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