storage_container_update

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

The description includes a risk level ('medium') and notes reversibility, but lacks details on potential side effects (e.g., data impact, downtime) and required permissions. With no annotations, more context would be beneficial.

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-line header with risk and reversibility, followed by a clear args list. Every sentence serves a purpose 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?

No output schema and no description of return value or operation behavior (async vs sync). The reversibility note is helpful, but the tool's context is incomplete for an agent to fully understand the effects.

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 the description explains each parameter's purpose: ext_id as identifier from list, max_capacity_bytes as optional, replication_factor as optional, and target as optional PC target. This adds significant value beyond the schema.

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 action 'Resize a container's capacity / replication' and specifies the resource as a storage container. It distinguishes from sibling tools that are read-only or create/delete operations.

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 explicit guidance on when to use this tool versus alternatives like storage_container_create or storage_container_delete. The description implies it's for resizing, but does not provide exclusion criteria or context.

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