docker_compose

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

No annotations provided, and the brief description does not disclose behavioral traits beyond the action names. For example, 'down' may destroy containers/networks but this is not stated. The tool relies entirely on the schema which lacks behavioral context.

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, which is concise but overly vague. It could be more informative without being verbose, e.g., listing key actions or constraints.

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 complexity (11 parameters, 10 actions, no output schema), the description is inadequate. Missing details like side effects of actions, required Docker Compose installation, and the impact of missing required parameters beyond 'action'.

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% so the schema already documents parameters. The description adds no additional meaning to parameters. Baseline 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?

Description 'Manage Docker Compose services' is somewhat generic but the schema's action enum (up, down, build, etc.) clarifies the tool's purpose. Distinguishes from sibling tools like docker_build or docker_containers by focusing on compose orchestration.

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 guidance on when to use this tool versus alternatives like docker_run, docker_build, or docker_containers. The description does not state prerequisites or typical scenarios.

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