KG Delete Entities Batch

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

Description adds cascade deletion of triples and return count of deleted entities and removed triples, going beyond annotations (destructiveHint, idempotentHint). Provides rich 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?

Two sentences with no waste. First sentence states action and limit, second sentence explains side effect and return value. Efficient.

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?

Covers key aspects: operation, limit, cascade, return values. With annotations and output schema (exists), it is sufficiently complete. Could mention idempotency but annotations already cover.

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 0% as description does not name parameters explicitly. However, it implies entity_ids via 'entities' and adds constraint 'up to 100'. Does not mention response_format parameter, but schema has enum and default.

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 clearly states verb 'delete', resource 'knowledge graph entities', batch constraint 'up to 100', and distinguishes from sibling kg_delete_entity by specifying batch capability.

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?

Provides explicit limit (up to 100) and cascade behavior, but does not explicitly tell when to use alternatives like kg_delete_entity for single or kg_add_entities_batch for add. Context is clear from sibling names.

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