IT Tools MCP Server

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

Annotations provide readOnlyHint=false, indicating this isn't a read-only operation (though conversion is typically non-destructive). The description adds that it converts 'between' formats, implying bidirectional functionality. However, it doesn't disclose important behavioral details like validation rules (e.g., Roman numeral syntax requirements), error handling for invalid inputs, or whether the conversion is lossless. With annotations covering basic safety, the description adds some context but misses key behavioral aspects.

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 - a single sentence that directly states the tool's function without any fluff. It's front-loaded with the core purpose and wastes no words. Every part of the sentence earns its place by specifying both conversion directions and the formats involved.

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 single-parameter conversion tool with good schema coverage but no output schema, the description is minimally adequate. It states what the tool does but lacks important context about validation rules, error conditions, output format, and differentiation from similar conversion tools. The absence of an output schema means the description should ideally mention what format the result takes, but it doesn't.

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, clearly documenting the single 'input' parameter as accepting Arabic numbers 1-3999 or Roman numerals. The description adds that conversion works 'between' these formats, reinforcing the parameter's dual-purpose nature. However, it doesn't provide additional semantic context beyond what the schema already states, such as format examples 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 clearly states the tool's purpose: converting between Arabic numbers and Roman numerals. It specifies both conversion directions and mentions the resource (numbers/numerals). However, it doesn't explicitly differentiate from sibling conversion tools like convert_number_base or convert_list, which could handle similar numeric transformations.

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. With many sibling conversion tools (convert_number_base, convert_temperature, etc.), there's no indication of when Roman numeral conversion is specifically needed versus other numeric transformations. No prerequisites, exclusions, or comparison to similar tools are mentioned.

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