Update Ploi Docker container

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

Annotations already indicate that this is a write operation (readOnlyHint=false) with possible side effects (openWorldHint=true) and no destruction (destructiveHint=false). The description adds that it updates name or deploy script but does not disclose authorization needs, operation idempotency, or response behavior. It does not contradict annotations.

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?

One concise sentence conveys the core operation without fluff. It is front-loaded with the verb and resource. Could be slightly more precise but is effective.

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?

The description lacks details on return value (no output schema), prerequisites (e.g., server and container must exist), or side effects beyond the update. For a straightforward update tool, this is acceptable but not complete.

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 100% with each parameter having a description. The description's mention of 'name or compose deploy script' roughly matches the schema's descriptions for those fields, adding no significant new meaning. Baseline is 3 due to high coverage.

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 the verb 'Update' and the resource 'Docker container', and specifies the modifiable attributes 'name or compose deploy script'. This distinguishes it from sibling tools like create (which creates a new container) and delete (which removes a container).

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 does not explicitly state when to use this tool versus alternatives or when not to use it. While it is clear from the name and siblings that this tool is for updating an existing container, the lack of explicit guidance lowers the score.

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