delete_element

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses permanence, which is a key trait, but it does not mention any required permissions, potential cascading effects on related elements, or whether the operation can be reversed (beyond 'permanently'). This is minimal for a mutation tool without annotation support.

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, well-structured sentence that front-loads the critical action ('Permanently delete') and the resource. It is concise with no wasted words, making it easy to parse.

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 delete tool with one parameter, the description is too sparse. It does not explain what constitutes an 'element', how to identify it, or what consequences deleting it has on the rest of the model. The existence of an output schema mitigates the need to describe return values, but the description still lacks essential context for safe usage.

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 has 0% description coverage, and the tool description does not mention the element_id parameter at all. It provides no guidance on what the parameter is, its format, or how to obtain it. The description fails to compensate for the schema's lack of detail, leaving the agent without essential parameter semantics.

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 ('delete'), a clear resource ('element'), and the scope ('from the model'). It is distinct from sibling tools like rename_element or create_element, and the word 'permanently' adds crucial irreversibility context.

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 want to remove an element), but it offers no explicit guidance on when not to use it or what alternatives exist (e.g., undo or soft delete). No exclusions or alternatives are mentioned, leaving the agent to infer context.

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