Deploy project

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

Annotations provide no special hints (readOnlyHint=false, destructiveHint=false). The description only repeats the command without disclosing behavioral traits like side effects (e.g., recreating containers, updating services) or potential impacts on running components. For a deployment tool, more behavioral context is expected.

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 an added one-line tip, no wasted words. The purpose is front-loaded for immediate understanding.

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 two required parameters and no output schema, the description provides the core action but misses details like return values, idempotency, or behavior when project is already running. It is minimally sufficient but not thorough.

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?

Both parameters (environmentId, projectId) are required and have schema descriptions ('Environment ID', 'Project ID'). The description adds no additional semantics beyond what the schema provides. With 100% schema coverage, baseline is 3.

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 specifies the action as 'Deploy a Docker Compose project' and includes the concrete command 'docker-compose up -d', making the purpose unambiguous. Among sibling tools, 'arcane_project_up' is distinct from 'arcane_project_down', 'arcane_project_redeploy', etc., and the description sets it apart as the initial deployment step.

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 explicitly recommends running 'arcane_project_pull_images' first to pull the latest images, providing a clear prerequisite. This helps guide the agent on proper sequencing, though it does not explicitly exclude alternative tools or scenarios.

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