IT Tools MCP Server

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

Annotations provide readOnlyHint=false (implying mutation), but the description doesn't add behavioral context beyond the basic operation. It doesn't explain what specific HTML entities get encoded, whether encoding is reversible, or any performance considerations. With annotations covering the safety profile, this earns a baseline score for adding minimal value.

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 maximally concise with just three words that directly convey the tool's function. There's zero wasted language, and the information is front-loaded perfectly.

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 simple transformation tool with good schema coverage and annotations, the description is adequate but minimal. It doesn't explain the output format or provide examples, which would be helpful given there's no output schema. The lack of differentiation from similar sibling tools is a notable gap.

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?

With 100% schema description coverage, the input schema already documents the single 'text' parameter thoroughly. The description doesn't add any additional semantic context about the parameter beyond what's in the schema, such as examples of input/output or edge cases.

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 'Encode HTML entities' clearly states the verb ('encode') and resource ('HTML entities'), making the purpose immediately understandable. However, it doesn't differentiate from the sibling tool 'encode_html_entities' which appears to serve a similar function, preventing a perfect score.

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 no guidance on when to use this tool versus alternatives like 'encode_html_entities' or 'decode_html'. There's no mention of specific use cases, prerequisites, or when this tool would be preferred over other encoding/decoding tools in the sibling list.

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