delete_entity

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

The description discloses a key behavioral trait: deleting an entity also deletes its relationships. However, with no annotations and a destructive operation, it would be important to mention that deletion is permanent, whether it requires specific permissions, and what happens to other dependent data like attributes. The partial disclosure is useful but not comprehensive.

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, direct sentence that communicates the essential action and scope without any filler. It is front-loaded and to the point, making it easy for an agent to parse quickly.

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 destructive tool with no annotations or output schema, the description is too sparse. It does not state what happens to attributes associated with the entity, whether deletion is irrevocable, if any prerequisites must be met, or what the success/failure response looks like. Given the tool's impact, the description leaves significant gaps in understanding for safe and correct invocation.

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 nicely describes the 'source' parameter with a detailed anyOf structure and explanation, but 'entityId' is left completely undocumented. The description adds no parameter-level meaning beyond what the schema already provides; it does not clarify what entityId refers to or how to format it. With only 50% schema coverage, the description should compensate for entityId but fails to do so.

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 clearly states the tool's action: 'Deletes an entity' and adds the important scope of 'including its relationships.' This effectively distinguishes it from sibling tools like delete_relationship, which targets only a relationship, and delete_attribute, which targets attributes.

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 gives no explicit guidance on when to use this tool versus alternatives. It does not mention when to prefer deleting an entire entity over deleting only relationships, nor does it address situations where the tool should be avoided. The single sentence implies usage by its verb, but lacks the necessary context to fully guide an agent.

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