remove_elements

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

The description goes well beyond the destructiveHint annotation by explaining that empty ids triggers total deletion, that confirm_delete_all is mandatory in that case, and that free nodes can optionally be removed. It also adds a critical rule prohibiting autonomous mass deletion without user permission.

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 front-loaded with the core action and organized into clear Args and warning sections. Some bilingual repetition adds length, but the critical safety instruction and example provide enough value to justify their inclusion.

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 three-parameter tool with no output schema, the description covers input formats, all parameters, the mandatory confirmation flag, and a worked example. Nothing essential to correctly invoking the tool is missing.

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 0%, but the description fully compensates by documenting all three parameters: ids supports int, list, or range string '1to10'; remove_free_nodes controls orphan node deletion; confirm_delete_all guards bulk deletion. This adds substantial meaning beyond the schema's minimal type/default information.

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 states a specific action ('Delete elements from the model') on a clear resource, and the ids parameter clarifies scope including partial or full deletion. Although sibling tools like remove_nodes and remove_section exist, the tool's focus on 'elements' distinguishes it sufficiently.

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?

Provides clear context for when ids can be left empty and explicitly states that confirm_delete_all must be true. It includes a strong LLM-specific instruction to ask the user before deleting all elements, but does not discuss alternatives or exclusions versus other removal tools.

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