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

The description discloses important behavioral details beyond annotations: invoke runs tools without installing them, install makes MCPs permanent, auth failures return connect links, and payment failures return checkout links. This adds substantial transparency beyond 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 long but information-dense; every sentence adds value. It is logically organized from core flow to install vs invoke to prompt library, though a single dense paragraph could benefit from bullet points or more distinct sections.

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 complex tool with many actions, the description covers the core flow, billing, admin requirements, and prompt library well. It misses a few details like the resume action, the immediate parameter, and the full set of return values, but overall it is quite complete.

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 23 parameters and 0% schema coverage, the description carries a heavy burden. It does explain the action parameter and implies tool_id and prompt variables, but many parameters (limit, query, arguments, immediate, prompt_*, cancel_reason) are not described. The core flow is clarified, but not every parameter's semantics.

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 identifies the tool as the official mcp.ai marketplace and explains its dual role as a catalog and execution engine. It explicitly distinguishes this tool from sibling openfinance and auth tools by describing the core flow of search → describe → invoke.

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?

The description provides explicit when-to-use guidance: prefer invoke for one-off runs, use install for permanent toolkit additions, and use search/describe for discovery. It also notes that writes require workspace owner/admin and explains the retry flow for connect/checkout links.

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