convert_docker_compose_to_run

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

The description lacks disclosure of any behavioral traits beyond the bare conversion; it doesn't mention that the tool does not execute commands, nor any limitations or side effects. Annotations only provide readOnlyHint false, which is not contradicted but offers little insight.

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 sentence with no unnecessary words, perfectly concise for a simple conversion tool.

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?

While the tool is simple with one parameter and no output schema, the description omits details about the output format (e.g., a single command or multiple), leaving the agent to infer. Adequate but not complete.

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 coverage is 100% (parameter content has a description), and the description adds no additional meaning beyond that provided in the schema.

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 action (convert) and resources (Docker Compose files to docker run commands), and distinguishes from sibling tool convert_docker_run_to_compose.

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?

No explicit guidance on when to use or alternatives, but the purpose is well-defined and the inverse sibling tool is present in the list.

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