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 full burden for behavioral disclosure. It states what the tool does but doesn't describe output format (e.g., hexadecimal string), whether the operation is deterministic, performance characteristics, or security considerations. For a cryptographic tool with zero annotation coverage, this represents significant gaps in behavioral context.

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 extremely concise (7 words) and front-loaded with the core purpose. Every word earns its place - 'Hash text' establishes the action, and the algorithm list provides essential context without redundancy. No wasted words or unnecessary elaboration.

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 cryptographic hashing tool with no annotations and no output schema, the description is incomplete. It doesn't explain what format the hash output takes (hexadecimal, base64, etc.), doesn't mention that the operation is deterministic and stateless, and provides no guidance on algorithm security implications. The description should do more given the tool's functional complexity.

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 fully documents both parameters (text and algorithm with default). The description adds no parameter semantics beyond what's in the schema - it doesn't explain algorithm differences, text encoding considerations, or output format. Baseline 3 is appropriate when schema does all the parameter documentation work.

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 specific action ('Hash text') and identifies the supported algorithms (SHA-256, SHA-512, MD5). It distinguishes this tool from sibling tools like encode-base64 or generate-uuid by specifying the cryptographic hashing function rather than encoding or generation operations.

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 implies usage context by listing algorithm options, but doesn't explicitly state when to use this tool versus alternatives like encode-base64 for encoding or generate-uuid for ID generation. It provides no guidance on algorithm selection or when not to use certain algorithms (e.g., MD5 for security-sensitive applications).

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