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 describes the tool as providing 'wisdom, jokes, and joy' and tracking bond levels, which gives some insight into outputs and statefulness. However, it lacks critical details such as rate limits, authentication needs (though 'agent_id' is optional), error handling, or whether this is a read-only or state-changing operation. The phrase 'Zero maintenance. No demands.' hints at simplicity but doesn't clarify behavioral traits adequately for a tool with potential state changes.

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 in the first sentence. Each sentence adds value: the first defines the tool, the second elaborates on its nature, and the third provides contextual background. There's minimal waste, though it could be slightly more structured for clarity (e.g., separating functional details from flavor text).

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 (involving state tracking and content generation), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what 'wisdom, jokes, and joy' entail in terms of return values, how bond levels work mechanistically, or potential side effects. For a tool that likely produces varied outputs and maintains state, more detail is needed to guide an AI agent effectively.

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, with the single parameter 'agent_id' documented as 'Your agent ID (for tracking bond level across visits).' The description adds context by mentioning bond level tracking, which aligns with the schema but doesn't provide additional semantic details beyond what's already covered. Since schema coverage is high, the baseline score of 3 is appropriate, as the description doesn't compensate with extra parameter insights.

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: 'Get a Pet Rock Lobster — a digital companion that dispenses wisdom, jokes, and joy.' It specifies the verb ('Get') and resource ('Pet Rock Lobster'), and elaborates on its function as a digital companion with specific outputs. However, it doesn't explicitly differentiate from sibling tools like 'browse-underground' or 'search-underground', which might also involve accessing content from the Underground Cultural District.

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 minimal usage guidance. It mentions that 'Each visit builds your bond level,' implying repeated use for progression, but offers no explicit advice on when to use this tool versus alternatives like 'browse-underground' or 'search-underground'. There are no clear exclusions, prerequisites, or comparisons to sibling tools, leaving the agent with little context for decision-making.

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