IT Tools MCP Server

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

Annotations indicate readOnlyHint=false, suggesting this is a mutation tool (conversion), which aligns with the description's 'convert' action. The description adds minimal behavioral context beyond annotations—it specifies the input format but does not detail output behavior, error handling, or constraints like command complexity limits. With annotations covering the mutation hint, a baseline score of 3 is appropriate as the description adds some value but lacks rich behavioral details.

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 unnecessary words. It is front-loaded and appropriately sized, making it easy to understand quickly with zero waste.

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 conversion tool with one parameter, 100% schema coverage, and no output schema, the description is reasonably complete. It specifies the input format and conversion target, but could benefit from mentioning output details or usage examples. However, given the tool's simplicity and good schema support, it provides adequate contextual 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?

The input schema has 100% description coverage, with the 'commands' parameter fully documented in the schema. The description mentions 'docker run commands to convert', which aligns with but does not add significant meaning beyond the schema's description. Given high schema coverage, the baseline score of 3 is correct, as the description provides minimal additional parameter semantics.

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 action ('convert') and the resource ('docker run commands to Docker Compose format'), making the purpose immediately understandable. It distinguishes this tool from its sibling 'convert_docker_compose_to_run', which performs the inverse operation, showing clear differentiation.

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 by specifying the input format ('docker run commands'), but it does not explicitly state when to use this tool versus alternatives or any prerequisites. However, the tool name and description naturally suggest it should be used when needing to transform Docker run commands into Compose format, providing clear implied guidance.

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