delete_entities

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

Discloses that relations associated with entities are also deleted, which is a critical side effect. No annotations provided, so description carries full burden. Could mention reversibility or permissions, but the core behavior is clear.

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?

Single sentence, no redundancy, directly conveys the tool's function. Every word contributes to understanding.

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?

One-parameter tool with no output schema. Description adequately explains input and effect. Could mention return type (e.g., success confirmation), but overall sufficient for a delete operation.

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% with one parameter documented. Description does not add semantic value beyond the schema, which already describes 'entityNames' as an array of strings. Baseline score of 3 is appropriate.

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?

Clearly states 'Delete multiple entities and their associated relations from the knowledge graph.' Identifies action (delete), resource (entities and relations), and scope. Distinguishes from sibling tools like delete_observations and delete_relations.

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 on when to use this tool vs alternatives. Does not explain that it cascades to relations, unlike delete_relations which only removes relations. Missing context for selection among siblings.

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