IT Tools MCP Server

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

Annotations provide readOnlyHint: false, indicating this is not a read-only operation, but the description doesn't add behavioral context beyond that. It doesn't explain what 'conversion' entails (e.g., mathematical calculation, no side effects, no authentication needs), though annotations cover the safety aspect. 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 that directly states the tool's purpose without any fluff. It's appropriately sized and front-loaded, making it easy for an agent 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 low complexity (simple conversion with three parameters) and high schema coverage, the description is minimally adequate. However, it lacks output details (no output schema) and behavioral context, making it incomplete for optimal agent use, though annotations provide some safety information.

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 descriptions for all parameters (temperature, from, to). The description adds no additional parameter semantics beyond what the schema provides, such as unit formats or conversion formulas, so it meets the baseline for high schema coverage.

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 temperatures between three specific units (Celsius, Fahrenheit, Kelvin). It uses a specific verb ('convert') and identifies the resource ('temperatures'), but it doesn't explicitly differentiate from sibling tools like convert_angle or convert_energy, which perform different types of conversions.

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 any prerequisites, constraints, or comparisons to sibling tools (e.g., convert_angle for angle conversions), leaving the agent with no usage context beyond the basic purpose.

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