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

Discloses that invoke runs one-off without installing, returns connect/checkout links, writes require owner/admin, and flags install states in search/describe. Complements annotations (readOnlyHint=false, openWorldHint=true) without contradiction.

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?

Dense and well-structured, front-loading the core flow and key invoke behavior, but it is long and covers many edge cases. Length is justified for a 23-param meta-tool, though it could be trimmed.

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 purpose, usage, auth/payment, install vs invoke, prompt library, and write permissions. With no output schema, it goes beyond typical descriptions; only per-parameter details are left out.

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 explains the core action enum and key parameters (tool_id, mcp_id), but many parameters (limit, query, prompt_vars, tier_slug, etc.) are left to inference. Adds significant meaning for the main flow, not exhaustive.

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 tool as the mcp.ai marketplace catalog and executor for MCP/tools, with a specific core flow (search→describe→invoke). Distinct from sibling tools like authenticate or show_version.

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 contrasts invoke vs install, states prefer invoke for one-off use, install for permanent; lists alternatives (search, describe, list_tools, request_mcp) and covers payment/auth retry flow.

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