resize_container_disk

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

No annotations are provided, so the description carries the full burden. It does not disclose behavioral traits like whether the container must be stopped, if data is preserved, or any side effects beyond resizing. The description only lists parameters.

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 extremely concise: a one-sentence summary followed by a clean args list. Every sentence is necessary and there is no redundant information.

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 an output schema exists (though not shown), the description doesn't need to detail return values. However, it lacks behavioral context like prerequisites, error conditions, or how it differs from sibling tools. It is adequate for a straightforward operation but could be more 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 coverage is 0%, so the description compensates by defining each parameter with examples: disk (e.g., 'rootfs', 'mp0') and size (e.g., '10G', '+2G'). This adds useful meaning beyond the schema types, though more detail on allowed formats could be helpful.

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 'Resize a container disk/volume' with a specific verb and resource. It distinguishes from sibling 'resize_vm_disk' by explicitly mentioning container, making it unambiguous.

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 like resize_vm_disk or other disk operations. There is no mention of prerequisites (e.g., container must be stopped) or context for use.

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