proxy_list_available_servers

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

The description reveals that the filter_tag parameter can act as a free-text query and uses search_servers for discovery, adding behavioral context beyond the schema. No annotation contradictions are present.

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 consists of two concise sentences, front-loading the purpose and then explaining the parameter. No extraneous or redundant information.

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?

The description adequately covers the purpose and parameter semantics. Given the simple tool and presence of an output schema, it is sufficiently complete, though it could mention the output format explicitly.

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 description coverage, the description fully explains the parameter's dual role as a tag filter or free-text query, significantly adding meaning beyond the type and default value.

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 verb 'List' and the resource 'MCP servers in the catalogue that are not yet mounted', effectively distinguishing it from the sibling tool 'proxy_list_active_servers' which lists already mounted servers.

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 indicates when to use this tool (to list unmounted servers) and implicitly contrasts with the sibling for active servers. While not explicit about alternatives, the context is clear enough for an AI agent.

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