VPS_restartProjectV1

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

The description discloses that containers are stopped and started in dependency order, and that data volumes and network configurations are preserved. With no annotations, this covers key behavioral traits, though it omits response details and prerequisites (e.g., project must be running).

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 concise (two short paragraphs) with the main action in the first sentence and supporting details immediately after. Every sentence adds value with no redundancy.

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 simplicity (2 required params, no output schema, no annotations), the description covers purpose, behavior, and use cases well. It could mention expected output or prerequisites, but is largely sufficient.

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% with clear parameter descriptions. The tool description does not add additional meaning beyond what the schema provides, meeting the baseline expectation.

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 tool restarts all services in a Docker Compose project with dependency ordering, distinguishing it from sibling tools like VPS_startProjectV1 (start only) and VPS_stopProjectV1 (stop only).

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 advises using the tool 'to apply configuration changes or recover from service failures,' providing clear use cases. While it does not list alternatives, the sibling names imply when to use start/stop instead.

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