IT Tools MCP Server

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations provide readOnlyHint=false, indicating it's not a read-only operation, but the description adds no behavioral context beyond the basic function (e.g., no info on error handling, performance, or side effects). Since annotations cover the safety profile minimally, the description adds little extra value, meeting the baseline for tools with annotations.

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 in the first sentence, followed by a concise, illustrative example. Every sentence earns its place by clarifying the tool's function without unnecessary details, making it highly efficient and well-structured.

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 (single parameter, no output schema, and annotations present), the description is complete enough for basic use. However, it could benefit from mentioning potential errors (e.g., invalid Base64 input) or output format, though the example partially addresses this. It adequately covers the essentials for a straightforward decoding tool.

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%, with the parameter 'text' fully documented in the schema as 'Base64 text to decode'. The description adds no additional meaning beyond the schema, such as format details or constraints, so it meets the baseline score when the schema does the heavy lifting.

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 ('Decode Base64 text back to original text') and the resource ('Base64 text'), with a concrete example that illustrates the transformation. It distinguishes itself from sibling tools like 'encode_base64' by focusing on the reverse operation.

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 when you have Base64-encoded text to decode, but it does not explicitly state when to use this tool versus alternatives (e.g., 'decode_url' or 'decode_html' for other encodings) or provide any exclusions. The context is clear but lacks explicit guidance on tool selection.

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