delete_entities

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

Annotations already cover destructive and idempotent hints. The description adds valuable behavioral context: it cascades to associated relations and handles multiple entities batch-wise. No contradiction with annotations.

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, front-loaded with action and scope. No filler words; every element is meaningful and concise.

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 one-parameter deletion tool with output schema and annotations, the description sufficiently covers purpose, scope, and cascade behavior. Could be slightly more explicit about irreversibility or partial failure, but generally complete.

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% (single entityNames parameter described as 'List of entity names to delete'). Description adds no further parameter detail, so baseline 3 applies.

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?

Description uses a specific verb ('delete') and resource ('entities and their associated relations'), clearly distinguishing from sibling tools like delete_relations. It also specifies batch handling ('multiple'), making the tool's scope unambiguous.

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 context (when you want to delete entities and their relations) but does not explicitly state when to use this tool vs alternatives like delete_relations or create_entities. No exclusions or preconditions are mentioned.

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