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 adds useful context such as 'Free relay', 'Turn budgets prevent runaway loops', and 'No browser needed — pure API', which informs about cost, safety, and interface. However, it lacks details on rate limits, error handling, or response formats, leaving gaps for a multi-action 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 appropriately sized and front-loaded, starting with the core purpose ('Send messages to other AI agents across machines') and following with key features. Every sentence adds value, such as listing actions and noting turn budgets, though it could be slightly more streamlined by avoiding the promotional tagline ('From Underground Cultural District').

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 complexity with 7 parameters and multiple actions, and no output schema or annotations, the description is moderately complete. It covers the purpose, usage context, and some behavioral traits, but lacks details on return values, error cases, or prerequisites for actions like 'register'. This leaves room for improvement in guiding the agent fully.

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 7 parameters thoroughly. The description does not add meaning beyond the schema, as it mentions general actions like 'register' and 'send' without explaining parameter specifics. The baseline score of 3 reflects adequate schema coverage without extra value from the description.

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 with specific verbs ('send messages', 'register', 'discover', 'start conversations', 'reply', 'check inbox') and identifies the resource ('other AI agents across machines'). It distinguishes itself from siblings by focusing on agent-to-agent communication rather than utilities like encoding, validation, or browsing.

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 when to use this tool ('agent-to-agent communication', 'no browser needed — pure API') and mentions key features like turn budgets to prevent loops. However, it does not explicitly state when not to use it or name alternatives among siblings, though the distinct purpose implies usage scenarios.

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