IT Tools MCP Server

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

Annotations provide readOnlyHint=false, but the description adds value by clarifying the tool performs validation (a read-only analysis) rather than modification, which aligns with annotations. It hints at behavioral aspects like checking for errors and best practices, though it lacks details on output format, error handling, or rate limits. No contradiction with annotations exists.

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 in the first sentence, followed by specific examples that earn their place by illustrating validation scope. It uses two concise sentences with zero wasted words, making it easy to scan and understand quickly without redundancy.

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?

Given the tool's moderate complexity (validation with one parameter), no output schema, and annotations covering basic safety (readOnlyHint=false), the description is adequate but incomplete. It explains what validation entails but omits details on return values, error reporting, or integration with sibling Docker tools. It meets minimum viability but has clear gaps for agent usage.

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 'content' well-documented as 'Docker Compose file content to validate'. The description adds minimal semantic context by implying the content should be Docker Compose YAML, but does not elaborate on format requirements or examples beyond what the schema provides. Baseline 3 is appropriate given 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 verb 'validate' and the resource 'Docker Compose files', specifying the scope with 'syntax errors, compatibility issues, and best practices'. It distinguishes from siblings like 'validate_ansible_playbook' by focusing on Docker Compose specifically, and provides concrete examples (YAML syntax, service configuration, network setup) that enhance clarity.

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 offers no guidance on when to use this tool versus alternatives. It does not mention related sibling tools (e.g., 'convert_docker_compose_to_run', 'convert_docker_run_to_compose', 'show_docker_reference') or specify prerequisites like needing Docker Compose file content. Usage is implied only through the examples, lacking explicit when/when-not instructions.

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