IT Tools MCP Server

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

Annotations provide readOnlyHint=false (implying potential side effects) but no destructiveHint. The description adds minimal behavioral context beyond annotations - it mentions 'show differences' which suggests a read operation, but doesn't clarify what 'show' means (output format) or whether comparison has side effects. With annotations covering basic safety, the description adds some value but lacks detail about output format or comparison methodology.

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 with zero wasted words. It's front-loaded with the core functionality and uses clear, direct language. Every word earns its place in this minimal description.

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 comparison tool with 2 parameters and 100% schema coverage, the description is adequate but minimal. No output schema exists, so the description doesn't explain what 'show differences' means in terms of return format. With annotations providing basic safety context, this is a minimum viable description that could benefit from more detail about output behavior.

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 no additional parameter semantics beyond what's already documented in the schema ('First text to compare', 'Second text to compare'). This meets the baseline expectation when schema does the heavy lifting.

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: 'Compare two texts and show differences' - a specific verb ('compare') and resource ('texts') with the outcome ('show differences'). It distinguishes from siblings like 'compare_json' which handles JSON specifically, but doesn't explicitly differentiate from other text analysis tools like 'analyze_text_stats'.

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 when to choose 'compare_text' over 'compare_json' (for JSON-specific comparison) or other text analysis siblings. There's no context about prerequisites, limitations, or typical use cases.

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