delete_elements

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

No annotations are provided, so the description carries the full behavioral burden and supplies almost nothing: it does not say the removal is destructive or irreversible, whether a snapshot/history entry is created, whether the provided label hooks into restore_snapshot, or what happens on a bad id. One sentence covering only the mechanical action is far short of what a delete tool needs.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity here reflects under-specification rather than disciplined editing.

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 required-parameter destructive operation with no annotations and no output schema, the description omits the essentials: reversibility, snapshot/label consequences, and behavior on missing or invalid ids. An agent could call it, but not safely.

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 67%: 'label' and 'scene' have solid schema descriptions, and the description's 'by id' at least clarifies the ids array's role. With parameters mostly self-documenting in the schema, this is a baseline adequate score, but the description adds no format or behavioral detail about the identifiers 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 states a specific verb and resource ('Remove elements') plus the selection mechanism ('by id'), so an agent knows exactly what the tool does. It does not, however, contrast itself with the many similar siblings (add_elements, move_elements, update_elements, replace_scene), leaving that differentiation to the tool names.

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?

There is no guidance on when to reach for this tool versus update_elements or replace_scene, nor any prerequisite or exclusion. The agent must infer usage purely from the name.

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