IT Tools MCP Server

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

Annotations provide readOnlyHint=false, indicating this is not a read-only operation, but the description doesn't add behavioral context beyond the conversion action. It doesn't specify what the output format looks like (e.g., single vs. multiple commands, error handling), performance considerations, or any side effects. With annotations covering basic safety, the description adds minimal value.

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, clear sentence that directly states the tool's purpose without unnecessary words. It's front-loaded with the core function and efficiently communicates the essential information. Every word earns its place, making it highly concise 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?

For a single-parameter tool with good schema coverage and annotations, the description is minimally adequate. However, it lacks output details (no output schema provided), doesn't explain conversion nuances (e.g., handling multi-service files, volume mappings), and offers no usage context. Given the complexity of Docker Compose conversions, more completeness would be beneficial.

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, clearly documenting the 'content' parameter as 'Docker Compose file content to convert'. The description doesn't add any additional parameter semantics beyond this, such as format requirements (e.g., YAML), size limits, or examples. With high schema coverage, the baseline score of 3 is appropriate.

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 function as 'Convert Docker Compose files to docker run commands' with a specific verb ('convert') and resource ('Docker Compose files'). It distinguishes from its sibling 'convert_docker_run_to_compose' by specifying the opposite conversion direction. However, it doesn't explicitly mention this distinction in the description itself.

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 the sibling tool 'convert_docker_run_to_compose' for reverse conversions, nor does it specify use cases like debugging, deployment, or learning Docker command-line equivalents. There's no mention of prerequisites or limitations.

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