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. It effectively describes key behaviors: it returns shops and products with specific fields (id, name, etc.), mentions filtering capabilities, notes that 23 products are free and most cost $1.99–$4.99, and implies a read-only operation without stating it explicitly. This adds valuable context beyond the input schema, though it could be more explicit about being a read-only tool.

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 front-loaded with the core purpose but becomes verbose with extensive examples and pricing details. While informative, some sentences (e.g., listing all shop examples and price ranges) could be more streamlined. It earns its place by adding context, but it lacks 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?

Given the tool's low complexity (1 optional parameter, no annotations, no output schema), the description is mostly complete. It covers purpose, usage examples, return fields, and pricing, which compensates for the lack of structured data. However, it could improve by explicitly stating it's a read-only browse operation and clarifying output format details, keeping it from a perfect 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 has 100% description coverage, so the schema already documents the 'shop' parameter as optional with partial match. The description adds some value by providing example shop names (e.g., 'angst-coffee-shop') and context about what they represent, but it does not significantly enhance the parameter semantics beyond what the schema provides. 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 tool's purpose: 'Browse Underground Cultural District — a marketplace of 228 digital products built for agents.' It specifies the verb 'browse' and the resource 'marketplace of digital products,' distinguishing it from sibling tools like 'buy-from-underground' (purchase) and 'search-underground' (search). The description provides concrete examples of what's available, making the purpose highly specific.

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 clear context for usage by listing example shops and categories (e.g., 'angst-coffee-shop' for existential beverages), which helps guide when to use this tool. However, it does not explicitly state when not to use it or mention alternatives like 'search-underground' for more complex filtering, so it falls short of a perfect score.

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