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

The description adds significant behavioral context beyond annotations: invoke runs one-off without bloating the toolkit, writes require workspace owner/admin, and credential/payment scenarios produce links that require user action before retry. These are non-obvious traits not captured by the schema or 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 a single, dense paragraph of roughly 350 words with no section breaks or bullet points. While each sentence adds substance, the lack of structural organization makes it difficult to quickly parse the core flow, permissions, and prompt library details, which could be separated into clearer segments.

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?

Despite missing output schema and minimal annotations, the description covers most essential context: core search/describe/invoke flow, one-off execution behavior, permission requirements, credential/payment edge cases, and the separate prompt library. Minor gaps remain (e.g., exact return format of search, role of `conversation` parameter), but for a complex multi-action tool it is largely 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 0% schema coverage, the description partially compensates by explaining key action values and the flow (e.g., 'describe returns one MCP's full profile', 'invoke RUNS that tool'). However, many parameters such as immediate, tier_slug, conversation, prompt_category, and report_context are never semantically defined, leaving ambiguity for a 23-parameter tool.

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's role: 'The official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them.' It further distinguishes itself from domain-specific siblings (e.g., contaazul_*) by framing itself as a meta-tool for discovery, management, and invocation of MCPs, plus a prompt library.

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?

Explicit usage guidance is provided: 'prefer invoke for a single/occasional use' and 'Use install only to make an MCP PERMANENT.' It also describes exactly when to expect connect/checkout links, how to retry, and when to use report_bug/request_mcp, giving clear selection criteria among actions and alternatives.

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