IT Tools MCP Server

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

Annotations indicate readOnlyHint=false, which aligns with the description's 'convert' action (implying computation, not mutation). The description adds context by specifying the bases involved, but doesn't disclose behavioral traits like error handling for invalid inputs, performance, or output format. No contradiction with annotations exists.

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 a single, efficient sentence with zero waste—it directly states the tool's function and includes relevant examples. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 moderate complexity (3 parameters, no output schema), the description is adequate but incomplete. It covers the basic purpose but lacks usage guidelines, error handling, or output details. With annotations providing some safety context, it meets a minimum viable level but leaves gaps for an AI agent to infer correct usage.

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 clear parameter descriptions in the schema. The description adds minimal value by implying the bases (binary, octal, decimal, hexadecimal) map to the 'fromBase' and 'toBase' parameters, but doesn't provide additional syntax or format details beyond what the schema already documents.

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 verb 'convert' and the resource 'numbers between different bases', with specific examples (binary, octal, decimal, hexadecimal) that illustrate the scope. However, it doesn't explicitly differentiate from sibling tools like 'convert_text_to_binary' or 'convert_roman_numerals', which handle different conversion types.

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. It doesn't mention prerequisites, edge cases, or compare it to similar sibling tools (e.g., 'convert_text_to_binary' for text-to-binary conversion vs. this tool for numeric base conversion).

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