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

The description discloses key behavioral traits beyond annotations: invoke runs tools even if not installed, returns connect/checkout links for auth/payment, and install adds permanent tools. It also notes permission requirements for writes, providing rich behavioral context that annotations alone (readOnlyHint=false, destructiveHint=false) do not capture.

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 front-loaded with a clear overview but is a single dense paragraph without bullet points or action-grouped sections, making it hard to scan. While the length is justified by the tool's complexity, better structure would improve readability.

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 tool with 14 actions, 23 params, and no output schema, the description covers the core flows, permissions, auth/payment handling, and prompt library adequately. It omits details on some parameters and return formats for specific actions like list_tools, but overall provides substantial context for such a complex 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?

With 23 parameters and zero schema descriptions, the description must compensate. It explains the action enum values and core parameters like tool_id and mcp_id, but leaves many parameters (immediate, tier_slug, cancel_reason, prompt_targets, etc.) ambiguous, so coverage is only partial.

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 states the tool is the official mcp.ai marketplace, serving as the catalog for MCPs/tools and the way to run them. It outlines a concrete flow (search → describe → invoke) and explicitly distinguishes its scope from sibling openfinance_* and utility tools, making its purpose unmistakable.

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 gives explicit usage guidance: prefer invoke for one-off tasks, use install only for permanent addition, and use list_tools to see what's callable now. It also states that writes require owner/admin and that request_mcp is for when nothing fits, providing clear when-to-use and when-not-to-use context.

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