update_container

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

Discloses it's a write operation with medium risk, captures prior limits, and supports dry_run. No mention of container state requirements, side effects like restart, or authentication needs. Moderate transparency for mutation tool without 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?

Concise two-sentence purpose followed by parameter list. Front-loaded with key info. Slight redundancy but overall efficient.

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 main behavioral aspects (undo, dry_run) and parameter details. Lacks explanation of return value or whether changes are synchronous. With 4 params, nested object, and no output schema, additional context on response would improve completeness.

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%, but description adds meaning by listing allowed resource keys (Memory, MemorySwap, etc.) and explaining dry_run and target. Container_id and target are clearly described. Compensates well for missing schema descriptions.

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?

Clearly states it updates a container's resource limits and captures prior limits for undo. Verb 'update' and resource 'container's resource limits' are specific. Distinguishes from sibling lifecycle tools like start_container, stop_container, 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?

Explains it is for updating resource limits and capturing prior limits for undo. Mentions dry_run for preview. Does not explicitly state when not to use, but context implies it's for resource modifications, not other container operations.

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