IT Tools MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It describes the conversion action but does not mention any behavioral traits such as error handling, performance, or side effects (e.g., whether it's read-only, requires specific inputs, or has limitations). This leaves gaps in understanding how the tool behaves beyond basic functionality.

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 concise and front-loaded, consisting of two clear sentences: one stating the purpose and another providing examples. There is no wasted text, and every sentence directly contributes to understanding the tool's use, making it 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 moderate complexity (3 parameters, no output schema, no annotations), the description is adequate but incomplete. It covers the basic purpose and examples but lacks details on output format, error cases, or behavioral context. Without annotations or an output schema, more information would be helpful for full contextual understanding.

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, documenting all parameters (value, fromUnit, rootFontSize) with details like enums and defaults. The description adds minimal value beyond this, only hinting at usage through examples without explaining parameter interactions or semantics. This meets the baseline of 3 when schema coverage is high.

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 REM and PX units for CSS, with specific examples (e.g., 1.5rem to pixels, 24px to rem). It distinguishes from sibling tools by focusing on CSS unit conversion, unlike other conversion tools (e.g., convert_temperature, convert_hex_to_rgb). However, it does not explicitly differentiate from all siblings, such as other unit converters, which prevents 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 implies usage through examples (e.g., converting 1.5rem or 24px), suggesting it's for CSS unit conversions. However, it lacks explicit guidance on when to use this tool versus alternatives (e.g., other conversion tools like convert_angle or convert_energy) or any prerequisites. The context is clear but not comprehensive, fitting a score of 3.

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