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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The phrase 'Featured/hot MCP servers' hints at curated content but does not explain what 'featured' or 'hot' means, nor does it describe the response format or any side effects. This is too sparse for a tool with no annotation support.

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 extremely concise, but it sacrifices useful context. While brevity is positive, the phrase lacks a verb and leaves the tool's exact behavior ambiguous, making it more under-specified than appropriately concise.

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 tool is simple (one optional parameter, output schema present), so the description does not need to explain return values. However, the ambiguity with 'list_trending' and the vague 'featured/hot' phrase leave the tool's purpose incompletely defined, preventing a higher score.

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 input schema fully covers the only parameter 'limit' with a clear description (max results, 1-50, default 20), achieving 100% schema_description_coverage. Since the schema does the heavy lifting, the description adds no additional parameter semantics, earning the baseline score of 3.

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 indicates this tool returns featured/hot MCP servers, aligning with the 'list' prefix in the name. However, it does not differentiate from the sibling tool 'list_trending', which may overlap in meaning, so it misses the distinction that would earn a 5.

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 guidance is provided on when to use this tool versus alternatives like 'list_trending' or 'search_servers'. The presence of similar sibling tools makes this omission a notable gap.

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