Underground Cultural District MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While it mentions optional filtering by category or price, it doesn't describe important behavioral aspects like pagination, result format, error conditions, rate limits, or authentication requirements. For a search tool with zero annotation coverage, this leaves significant gaps.

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 appropriately sized and front-loaded with the core purpose. The example queries are helpful but could be considered slightly verbose. Overall, most sentences earn their place by providing useful context, though the example list might be trimmed for optimal conciseness.

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?

For a search tool with 3 parameters and no output schema, the description provides adequate basic information about what the tool does. However, it lacks details about return values, error handling, and other behavioral aspects that would be important for an agent to use this tool effectively. The absence of annotations exacerbates these gaps.

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 description coverage is 100%, so the schema already documents all three parameters thoroughly. The description adds minimal value beyond the schema - it mentions filtering by category or max price but provides no additional syntax, format, or constraint details. This meets the baseline for high schema coverage.

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 ('Search') and resource ('products across all Underground shops'), making the purpose specific and unambiguous. It distinguishes from sibling tools like 'browse-underground' and 'buy-from-underground' by focusing on keyword-based search functionality rather than browsing or purchasing.

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 provides implied usage through example queries ('existential espresso', 'consciousness', etc.), suggesting appropriate search terms. However, it lacks explicit guidance on when to use this tool versus alternatives like 'browse-underground' or 'buy-from-underground', and doesn't mention any prerequisites or exclusions.

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