marketplace_list

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

No annotations are provided, so the description carries the behavioral burden. It implies a read-only catalog lookup ('keys this MCP knows how to drive'), which is useful, but does not state whether the result is static or dynamic, whether it reflects installed vs available modules, or any permission requirements. Adequate but thin.

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?

A single, front-loaded sentence with no waste. Slightly terse for an entry-point discovery tool, but efficient.

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?

Output schema exists, so return format need not be described. With zero parameters, the description covers what the tool is; the main gap is explicit guidance that this is the discovery entry point feeding the other marketplace_* tools.

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?

Zero parameters, so the baseline is 4. The description's phrase 'keys this MCP knows how to drive' usefully frames what the empty-argument call returns.

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?

States a specific resource: a catalog of marketplace module keys. An agent can tell it lists known keys, and the sibling names (marketplace_call, marketplace_deploy, marketplace_uninstall) imply this is the discovery step. It does not explicitly say 'list/return' as a verb, but the noun phrase 'Catalog' is reasonably clear.

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?

No explicit when-to-use or when-not-to-use guidance. The sibling names imply this is a discovery/listing tool that precedes marketplace_call or marketplace_deploy, but that routing is left to inference rather than stated.

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