validate_docker_compose

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

The description claims validation (read-only behavior) but annotations set readOnlyHint to false, contradicting the safe nature of validation. This inconsistency misleads agents about potential side effects.

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 two sentences, front-loaded with the primary action, and includes an illustrative example. Every word contributes to clarity with zero fluff.

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?

As a validation tool with no output schema, the description omits crucial details about what the tool returns (e.g., pass/fail, error list). This is a significant gap for agents to interpret results.

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 single parameter 'content' is fully described in the schema (100% coverage). The description does not add extra meaning beyond specifying the file content, so it meets the baseline but provides no additional value.

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 explicitly states it validates Docker Compose files for syntax errors, compatibility, and best practices, with a concrete example. It clearly distinguishes from sibling validation tools like validate_ansible_playbook and validate_iban.

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 when a Docker Compose file needs validation but offers no explicit when-to-use, when-not-to-use, or alternatives. It lacks guidance on distinguishing from related tools like convert_docker_compose_to_run.

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