docker_compose_up

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

The description adds no behavioral context beyond the idempotentHint annotation. It does not mention that 'detach' defaults to true, that 'build' triggers a build before starting, or any side effects like network/volume creation. With annotations present, the bar is lower, but the description still fails to disclose useful behavioral traits.

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, concise sentence with no fluff. It is front-loaded and directly states the action, earning a perfect score for efficiency.

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 has 4 parameters, no output schema, and sibling tools with overlapping functionality, the description is too terse. It lacks information about return values, behavior when services are already running, and the meaning of detach/build parameters. This leaves the agent under-informed for a reasonably complex operation.

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 75% (three of four parameters have descriptions), so the schema does most of the heavy lifting. The tool description adds no parameter-level information, leaving project_dir undocumented. Baseline 3 is appropriate as the description does not hinder but also does not enhance 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 'Start Docker Compose services' uses a specific verb and resource, clearly distinguishing it from siblings like docker_compose_down, docker_compose_logs, and start_container. The phrase 'Compose services' differentiates it from container-level operations.

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 is provided on when to use this tool versus alternatives such as start_container or docker_compose_down. The description lacks context about prerequisites, when to choose this over other tools, or any exclusions.

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