maltego_delete_entity

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

Beyond annotations (destructiveHint, idempotentHint), description adds that it removes all links touching the entity and returns confirmation including number of links removed or an error. This provides clear behavioral context for a destructive operation.

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 concise with one sentence for the action and a structured Args/Returns block. It avoids unnecessary words, though the Args format could be integrated more naturally. Efficient overall.

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 deletion tool with an output schema (return value described), the description covers the main effect, return type, and error condition. It does not specify what happens if the entity doesn't exist, but that is acceptable for a simple destructive tool. Sufficient for use.

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 input schema already describes entity_id with 'Id of the entity to delete (its links are removed too).' The description repeats this information without adding new meaning. With schema description coverage effectively 100% (the single parameter is described), the additional description is redundant but not harmful.

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 'Delete an entity and all links touching it from the active graph.' This specifies the verb (delete), resource (entity and its links), and scope (active graph). It distinguishes from sibling tools like maltego_delete_link (only links) and maltego_delete_graph (entire graph).

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?

Lacks explicit guidance on when to use this tool vs alternatives such as maltego_delete_link. Does not mention prerequisites (e.g., entity must exist) or when not to use it. The phrase 'from the active graph' implicitly indicates the context but does not fully guide selection.

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