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

Discloses significant behavioral details beyond annotations: invoke works even for non-installed MCPs and runs one-off without bloating the toolkit; install makes permanent; search/describe flag installation status; writes require admin. Also explains return behaviors like connect/checkout links. No contradictions with 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 lengthy wall of text covering many facets. While it is front-loaded with the purpose, it rambles into extensive detail and includes redundant explanations (e.g., repeated mentions of connect/checkout). A more structured breakdown per action would be far more scannable. It is not concise; every sentence does not earn its place relative to the overload.

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 complexity (23 params, many actions, no output schema), the description is fairly complete at the flow level: it explains the main actions, auth requirements, and expected behavior (links, installs). However, it leaves many parameters unexplained and does not cover every action's specific inputs (e.g., request_details, cancel_reason, prompt_targets). Still, for a first-pass understanding, it is largely sufficient.

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 coverage is 0%, so the description must compensate. It explains the high-level meaning of action enums (search, describe, invoke, etc.) and some parameters indirectly (e.g., tool_id, arguments for invoke), but does not clarify most of the 23 parameters (limit, query, mcp_id, message, immediate, tier_slug, prompt_* etc.). Many parameters remain opaque, leaving the agent without enough detail to correctly construct calls.

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 it is the official marketplace catalog and runner, with a detailed breakdown of actions. It effectively distinguishes from sibling tools like report_bug (which is a sub-action here) and covers core functionality, though it is a multi-purpose tool with many functions.

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?

Provides explicit guidance on when to use each action: core flow (search → describe → invoke), prefer invoke over install for one-off uses, use install for permanence, and mentions billing actions like subscribe/cancel. Also includes conditional flows (connect link for auth, checkout for payment) and notes that writes require owner/admin. Clearly defines when and when not to use alternatives.

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