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

Beyond the annotations, the description discloses that invoke runs one-off without installing, returns connect/checkout links requiring user action then retry, and that writes need owner/admin. It also covers billing, installed flags, and prompt-library behavior, with no contradiction to the 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 and front-loaded with the core flow, and every sentence adds information. It is a long single paragraph with mixed-language phrasing ('pontualmente'), so slightly less concise/structured than a bulleted version, but still efficient for a 14-action tool.

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 high-complexity tool with 23 params, no output schema, and no required params, the description covers the full action surface, auth requirements, billing edge cases, install-vs-invoke semantics, and the prompt library. The only minor gap is not detailing every action-specific parameter, but the core flow and return-link behaviors are sufficiently specified.

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 compensates by explaining action values, tool_id selection, arguments, prompt_vars, prompt_slug, and tier/pricing context. However, several params (resume, immediate, conversation, cancel_reason, report_context, request_details) are left to their schema names, 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 opens with 'official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them' and then lays out the core search→describe→invoke flow. It clearly distinguishes the tool from siblings by positioning it as the catalog-and-execution hub, not just a single-purpose utility.

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?

It explicitly contrasts invoke vs install ('prefer invoke for a single/occasional use'; 'Use install only to make an MCP PERMANENT'), explains when connect/checkout links appear, and directs request_mcp to 'when nothing fits'. It also states write operations require workspace owner/admin, giving clear when-to-use and exclusion guidance.

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