Delete Entity

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

The description adds 'permanently,' which conveys irreversibility beyond the destructiveHint annotation's basic destructive classification. It also makes the handle-based targeting explicit, though it does not describe failure modes or cascade effects; annotations already cover the read-only/destructive profile.

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 states the action and the key qualifier ('permanently') before the parameter. Every word earns its place with no filler.

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 one-parameter destructive operation with a high-coverage schema, an output schema, and safety annotations, the description covers what the tool does and how to identify the target. It is slightly light on guidance about batch alternatives, but that gap is already captured in usage guidance.

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 100%, and the handle parameter is already described in the schema as 'Entity handle to delete.' The description's 'by its handle' reinforces the parameter's role but adds no new format, source, or validation details.

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 a specific verb ('delete'), names the resource ('entity'), and specifies the selection mechanism ('by its handle'). It clearly distinguishes from sibling tools like entity_delete_many because it identifies single-entity deletion by handle.

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?

No guidance is given about when to choose this tool over alternatives. The presence of entity_delete_many suggests a related batch operation, but the description does not mention it or provide selection criteria.

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