lattice_update_container

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

No annotations are provided, so the description bears full responsibility. It discloses that the tool changes the stored record and requires redeploy/recreate, adding behavioral context. However, it omits details about partial updates, validation, error conditions, or the impact on running containers.

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 two sentences, immediately stating the action and key consequences, with no unnecessary words.

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 the complexity (14 parameters, no output schema, low schema coverage), the description is insufficient. It lacks details on return values, error handling, prerequisites, and partial updates, making it incomplete for effective tool usage.

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?

With only 29% schema coverage, most parameters lack descriptions. The description does not add any parameter-specific semantics beyond implying the 'id' is required. It fails to compensate for the low coverage, leaving the agent without guidance on parameter usage.

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 it updates a container definition, specifying 'update' as verb and 'container definition' as resource, and distinguishes from sibling tools like create_container or delete_container by indicating it modifies an existing record.

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 advises that redeploy or recreate is needed for changes to take effect, providing clear context for post-update actions. However, it does not explicitly mention when not to use this tool or compare it to alternatives like lattice_create_container or lattice_recreate_container.

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