list_mcp_servers

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

With no annotations provided, the description carries the behavioral burden. It discloses the output fields, the 'hosted' scope, and the privilege requirement. However, it does not explicitly state that this is a read-only operation or describe error behavior (e.g., what happens without privilege), leaving some gaps for a mutation-free list operation.

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?

Two sentences, front-loaded with the main action, followed by essential details (output fields, sibling distinction, privilege). Every word earns its place; no fluff or repetition.

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 low complexity (no params, simple list operation) and absence of an output schema, the description provides sufficient context by listing the return fields, naming the sibling alternative, and noting the privilege requirement. It could be slightly more complete by mentioning pagination or ordering, but these are not essential for a straightforward list tool.

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?

The tool takes no parameters (empty schema, 100% coverage by default). The baseline for zero parameters is 4, and the description provides no parameter-specific details that could mislead. It correctly stays silent on parameters.

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 uses a specific verb 'List' with a clear resource 'AI Hub hosted MCP servers' and specifies the exact fields returned. It also explicitly distinguishes itself from the sibling tool list_api_collections, making its purpose unambiguous.

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 explicitly names an alternative tool (list_api_collections) and clarifies the scope (AI Hub hosted). It also states the prerequisite 'Needs the MCP privilege.' This gives clear context for when to use this tool, though it doesn't explicitly say when not to use it beyond the distinction.

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