delete_entities

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

The description discloses the CASCADE effect on observations and relations and FTS index cleanup. Since no annotations are provided, it carries the full burden, but could mention irreversibility or permission requirements. Still, it provides good behavioral context.

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 extremely concise: two sentences that front-load the action and key effects. Every sentence adds value without redundancy.

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?

Given the tool's simplicity (one parameter, clear action) and the presence of an output schema, the description is mostly complete. It explains the primary effect and side effects, though it omits details about the parameter format and any return value.

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 0%, and the description does not explain the 'entityNames' parameter beyond its name. For a simple array parameter, it should at least specify that entity names must exist or follow a format. The description fails to compensate for the lack of schema documentation.

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 deletes entities and cascades to observations and relations, with FTS index cleanup. It uses specific verbs and resources, and distinguishes itself 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?

The description implies usage for deleting entities with their associated data, but it does not explicitly state when to use this tool over alternatives like delete_observations or delete_relations, nor are there any exclusions provided.

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