IT Tools MCP Server

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

Annotations provide readOnlyHint=false, indicating this is a mutation operation. The description 'Convert text to lowercase' implies transformation behavior but doesn't add meaningful context beyond what annotations already convey. It doesn't describe error handling, character set limitations, or whether the operation is idempotent. With annotations covering the basic safety profile, the description adds minimal behavioral insight.

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 perfectly concise at just three words. It's front-loaded with the core action and contains zero wasted words. Every element ('Convert', 'text', 'to lowercase') earns its place by communicating essential information efficiently.

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 transformation tool with one well-documented parameter and basic annotations, the description is minimally adequate. However, it lacks context about output format (though no output schema exists), doesn't explain when to use this versus other text tools, and provides no behavioral details beyond the obvious transformation. Given the tool's simplicity, it's complete enough to understand the basic operation but misses opportunities for better guidance.

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 with the 'text' parameter clearly documented as 'Text to convert to lowercase'. The description doesn't add any parameter information beyond what the schema already provides. According to scoring rules, when schema_description_coverage is high (>80%), the baseline is 3 even with no param info in the description.

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 'Convert text to lowercase' clearly states the verb ('convert') and resource ('text') with the specific transformation ('to lowercase'). It distinguishes from sibling tools like 'capitalize_text' and 'convert_text_to_uppercase' by specifying the lowercase operation. However, it doesn't explicitly differentiate from other text transformation siblings like 'convert_text_to_camelcase' beyond the obvious operation name.

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 lowercase conversion is appropriate (e.g., for normalization, case-insensitive comparisons) or when other text transformations might be better suited. With many sibling text tools available, this lack of contextual guidance is a significant gap.

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