stape_update_container

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

With no annotations, the description must disclose behavioral traits on its own, but it only says 'Update settings' and fails to mention side effects, reversibility, partial-update semantics, required permissions, or what the response contains. The mutation implication is present, but the operational details are absent.

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 a single, focused sentence with no fluff, front-loading the action and resource. It could have included more useful context (e.g., that only specified fields are updated) without becoming verbose.

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?

Although the schema documents parameters, the description gives no information about update behavior (partial vs. full replacement), return values, error cases, or prerequisites for existing containers. There is no output schema, so the absence of return-value context is a notable gap.

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?

The input schema covers 100% of parameters with descriptions, so the baseline is 3. The description adds no additional parameter-level meaning; the optionals are already self-explanatory from the schema, and the required container_identifier is clear.

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 states a specific action ('Update settings') and identifies the resource ('existing Stape container'), clearly distinguishing it from sibling tools like stape_create_container or stape_delete_container. However, 'settings' is a broad term and could be more precise about which attributes are updatable, though the schema partially covers that.

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 provides no guidance on when to use this tool versus alternatives, such as preferring stape_get_container for reads or stape_create_container for new containers. There is no mention of prerequisites, such as the container must already exist or which plan/region combinations are valid.

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