VPS_updateProjectV1

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

Discloses that data volumes are preserved and that it pulls latest images and recreates containers. No annotations provided, so description carries burden; could mention potential downtime or rollback behavior.

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?

Three sentences, each earning its place: action, behavioral detail, use cases. Front-loaded and no wasted words.

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?

Covers core operation, volume preservation, and use cases. No output schema or annotations, but could mention prerequisites like project existence or service interruption.

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 baseline 3. Description does not add parameter-level details beyond the schema descriptions, which are adequate.

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 it updates a Docker Compose project by pulling latest images and recreating containers. It distinguishes from siblings like VPS_createNewProjectV1, VPS_deleteProjectV1, etc.

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?

Explicitly says 'Use this to deploy application updates, apply configuration changes, or refresh container images to their latest versions.' Doesn't mention when not to use or that the project must exist, but context from siblings implies it.

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