delete_elements

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

With no annotations provided, the description carries the full behavioral burden. It discloses that deletion is soft and that Excalidraw keeps tombstones for peer convergence. This is meaningful beyond simply saying 'delete', though it does not cover reversibility, permissions, or what happens to tombstoned elements.

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, front-loaded with the action and target, and includes a concise parenthetical explanation of the tombstone behavior. No filler or redundancy.

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 simple one-parameter tool with no output schema, the description covers what the tool does, the target resource, and the important soft-delete side effect. It is mostly complete, though explicit usage exclusions and note about response/return behavior would make it fully complete.

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?

The input schema only defines an 'ids' array of strings; the description clarifies these are element ids being soft-deleted. Since schema description coverage is 0%, this is some compensation, but it does not explain id format, behavior for missing ids, or whether all ids must be valid.

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: 'Soft-delete elements by id'. It also clarifies the deletion mode (soft vs hard) and clearly differentiates itself from sibling tools like add_elements, update_elements, and read_scene.

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 the tool is for removing elements, and the 'soft-delete' phrasing hints that it should be used when tombstones/peer convergence are desired. However, it does not explicitly state when to use this tool versus alternatives, when not to use it, or any prerequisites.

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