IT Tools MCP Server

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

Annotations provide readOnlyHint=false (implying mutation), but the description adds valuable behavioral context: it describes the transformation logic with concrete examples showing how spaces and hyphens are handled. This goes beyond annotations, though it doesn't cover edge cases like numbers or special characters.

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 front-loaded with the core purpose, followed by illustrative examples. Every sentence earns its place by clarifying the transformation. No wasted words or redundant information.

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 text transformation tool with one parameter, 100% schema coverage, and no output schema, the description is reasonably complete. It explains the behavior with examples, though it could note limitations (e.g., handling of numbers, punctuation). The annotations cover safety, and the purpose is clear.

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 the parameter 'text' fully documented in the schema. The description doesn't add any parameter details beyond what's in the schema, so it meets the baseline of 3 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 specific verb ('convert') and resource ('text to camelCase format'), and distinguishes itself from sibling tools like convert_text_to_kebabcase, convert_text_to_pascalcase, etc. by explicitly naming the target format. The examples further clarify the transformation.

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 context through examples (e.g., converting spaces and hyphens), but doesn't explicitly state when to use this tool versus alternatives like convert_text_to_kebabcase or convert_text_to_pascalcase. No exclusions or prerequisites are mentioned.

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