docker_deploy_scenario

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

Without annotations, description partially informs that operation is read-only by stating 'Return the docker-compose command', but lacks details on prerequisites, error handling, or 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?

Two sentences, front-loaded with purpose, no extraneous information. Highly concise and well-structured.

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 presence of output schema (inferred from context), description is adequate. Could be improved by explicitly stating that the command is not executed and by suggesting docker_list_scenarios for scenario discovery.

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?

Description adds examples of valid scenario names (e.g., load-balancer, class4-sbc), which provides context beyond the schema's minimal title. However, does not reference the sibling tool docker_list_scenarios for available names.

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 clearly states verb 'Return' and resource 'docker-compose command to deploy a specific scenario'. Differentiates from sibling tools like docker_list_scenarios and sipp_run_scenario.

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. Does not specify that it only returns the command without executing deployment, nor contrasts with similar tools.

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