lattice_recreate_container

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

The description only states 'remove and create fresh' without detailing behavioral traits. No annotations exist, so the description must disclose potential side effects (e.g., data loss), error states, or dependencies. It fails to warn that this is a destructive operation that may permanently delete the container's state.

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 minimal (one short sentence) and front-loaded with the core purpose. It wastes no words, but additional context could be added without sacrificing conciseness.

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?

For a destructive operation with no output schema and no annotations, the description should provide more context about return values, error handling, or post-conditions. It is insufficiently complete for safe and effective 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?

Schema description coverage is 100% for the single parameter 'id', which is described as 'Container ID'. The tool description adds no extra meaning beyond what the schema already provides, so baseline 3 applies.

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 verb-reource: 'Recreate a container (remove and create fresh)'. This distinguishes it from sibling tools like 'remove_container' and 'create_container' by combining both actions into a single operation.

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 removing and creating separately. No context about prerequisites, conditions, or scenarios where recreate is preferred over other container lifecycle tools.

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