delete_entity

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

With no annotations, the description carries the behavioral burden, and it clearly flags the operation as destructive and requires confirmed:true before execution. It does not disclose permanence, cascading effects, or reference cleanup, but the core safety hazard is prominently communicated.

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?

One efficient sentence with the key safety warning placed immediately after the action. There is no filler or redundant text.

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 two-parameter guarded delete operation, the definition provides the essential invocation context: target, destructive nature, and required confirmation. It is slightly thin on post-conditions and return behavior, but this is a minor gap at this complexity level.

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 100%, and both parameters are clearly documented: name and confirmed. The description adds emphasis on the confirmed:true precondition but no new format, default, or edge-case meaning beyond the schema.

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 action ('delete') and resource ('entity page'), which clearly separates it from siblings like delete_concept and create_entity/update_entity. It does not explicitly name alternatives or clarify what an 'entity page' is, so it stops short of full differentiation.

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 when-to-use or when-not-to-use guidance is provided. It does not mention that update_entity should be used for modifications or that verification via read_entity/list_entities may be needed before deletion. The only implicit trigger is 'delete an entity', which is too weak for choosing among closely related entity tools.

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