lattice_remove_container

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

With no annotations, description must carry full behavioral burden. It only states the action without disclosing consequences (e.g., irreversible? permission needs? impact on associated resources?).

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?

Extremely concise single sentence with no fluff. However, brevity comes at cost of necessary detail for a destructive action.

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 presence of sibling tools with overlapping semantics, description is insufficient. No explanation of 'entirely' or distinction from similar tools like lattice_delete_container or lattice_force_remove_container.

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 100% (parameter 'id' described as 'Container ID'). Description adds no extra meaning beyond schema, baseline score 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?

Description "Remove a container entirely" clearly identifies verb and resource, but does not differentiate from similar siblings like lattice_delete_container or lattice_force_remove_container, leaving ambiguity.

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 (e.g., delete vs force_remove). Lacks context on prerequisites or exclusions.

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