KG Delete Entity

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

Annotations already indicate destructive and idempotent behavior. The description adds crucial transparency by revealing the cascading side effect (deletes all triples referencing the entity), which goes beyond the 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?

Two concise sentences: the first states the primary action, the second explains the cascading behavior. No unnecessary words, effectively front-loads the core purpose.

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?

The description covers the essential behavior (deletion with cascade) and is aided by annotations (destructive, idempotent) and an output schema. It could mention idempotency explicitly, but overall it provides sufficient context for the tool's 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?

The schema has 2 parameters (entity_id, response_format) with 0% schema description coverage. The description adds no information about these parameters. While entity_id is self-explanatory, response_format's role in controlling output format is not explained, which is a gap.

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 specifies the action 'Delete', the resource 'knowledge graph entity by ID', and the key behavior 'Cascades: also deletes all triples where the entity is subject or object.' This clearly distinguishes it from sibling tools like batch delete or add.

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 explicitly mentions cascading deletion, implying when to use this tool (for deleting an entity and its associated triples). However, it does not provide explicit guidance on when not to use it or alternatives like localnest_kg_delete_entities_batch.

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