delete_element

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

With no annotations, the description must disclose behavioral traits. 'Remove' implies destructiveness but does not explicitly state irreversibility, permission requirements, or what happens if the element does not exist. It only mentions the return value briefly, leaving notable gaps for a destructive operation.

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 a single sentence, concise and front-loaded with the main action. It wastes no words and effectively communicates the core operation and return value.

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 tool's simplicity and lack of annotations, the description is minimally adequate: it states the action and return value. However, it omits important context such as the role of page_id, the meaning of base_rev, error behavior, and whether deletion is permanent, making it incomplete for full operational clarity.

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%, so the description must compensate. It clarifies that element_id is the ID of the element to remove, but page_id and base_rev remain unexplained. The phrase 'by id' only partially covers the parameter semantics, leaving most parameters under-specified.

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 uses the specific verb 'Remove' with the resource 'element from a canvas by id,' clearly differentiating it from sibling tools like update_element or add_element. It also specifies the operation is for exactly one element, which prevents confusion with bulk operations.

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 implies when to use it (when you need to delete a single element by ID) but does not provide explicit exclusions or alternatives, such as when to use update_element or patch_canvas instead. There is no mention of prerequisites like existing page or element.

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