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 mentions the 'now' functionality and implies conversion behavior, but doesn't describe error handling, timezone considerations, or output format details. It provides basic operational context but lacks depth for a tool with 3 parameters and no output schema.

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 perfectly concise with two sentences that each earn their place: the first states the core functionality, and the second provides a specific usage tip. It's front-loaded with the main purpose and wastes no words, making it highly efficient for an AI agent.

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 3 parameters with low schema coverage (33%) and no output schema, the description is somewhat incomplete. It covers the basic conversion purpose and 'now' functionality but doesn't explain parameter roles, output formats, or edge cases. For a conversion tool with multiple input options, more context would be helpful, though the concise nature keeps it minimally viable.

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 only 33% (only the 'value' parameter has a description), so the description must compensate but adds minimal parameter semantics. It mentions 'now' as a value option, which aligns with the schema's enum for 'from', but doesn't explain the 'from' and 'to' parameters or their enum values. The description provides some context but doesn't fully bridge the coverage gap.

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 ('convert between') and resources (Unix epoch, ISO 8601, human-readable date strings), distinguishing it from sibling tools like convert-eth-units or decode-base64. It explicitly mentions the 'now' functionality, which adds specificity beyond a generic conversion tool.

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 (timestamp conversion) and includes a specific usage example ('Pass 'now' as value for current time'), but it doesn't explicitly state when not to use it or name alternatives among siblings. The context is sufficient for typical use cases without explicit exclusions.

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