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

The description substantially expands on the annotations by revealing key behaviors: invoke works even without installation, does not bloat the tool list, returns connect links for missing credentials, returns checkout/top-up links for paid tools, and requires owner/admin for writes. It does not contradict the annotations, and the openWorldHint is appropriately reflected in the broad catalog behavior.

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 and every section earns its place: core flow, temporary vs permanent invocation, billing/auth implications, write permissions, and the prompt library. It is not formatted as concise bullets, but the paragraph structure is acceptable for a multi-action tool and the KEY sentence front-loads the most important behavior.

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 high complexity (14+ actions, 23 parameters, no output schema), the description covers the main flows well and supplies enough context for selecting the right action. It leaves some return-value details and parameter mappings vague, but for a tool this broad, the level of completeness 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?

Schema description coverage is 0% with 23 parameters, so the burden is on the description. It adds important meaning for action values, the action=search -> describe -> invoke flow, and the role of tool_id and prompt_vars. However, many parameter names are still only implied or not explained at all (limit, immediate, tier_slug, conversation, report_context, prompt_targets, request_details, etc.), so the description only partially compensates for the schema's silence.

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 marketplace as the in-platform catalog and execution layer for MCP/tools. It names concrete verbs and resources (search, describe, invoke, install, subscribe/cancel, prompt-library actions) and explains what each does, which strongly distinguishes the tool's broad but well-defined scope.

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 when-to-use guidance and names alternatives: use invoke for one-off runs, install only for permanent toolkit additions, list_tools for what is callable now, request_mcp for missing capabilities, and search_prompts/get_prompt for prompt text. It also flags prerequisites like workspace owner/admin for writes.

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