delete_relations

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

No annotations are provided, so the description must convey behavioral traits. It omits important details such as whether deletion is permanent, if it returns confirmation, or error behavior for missing relations. The description only covers input format, not the consequences of the action.

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 redundancy. The first sentence states the purpose, and the second clarifies the input format. It is front-loaded and succinct.

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 no annotations, the description is incomplete. It does not explain the return value (though output schema exists), error handling, idempotency, or whether the entire graph is affected. The required fields are specified, but additional allowed properties are not mentioned. Overall, the description covers basic usage but leaves gaps in expected behaviors.

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 0% description coverage and the items schema is loosely defined with additionalProperties: true. The description adds critical semantic information by specifying the required keys (from, to, relationType) and their types (str), which is not enforced by the schema. This adds significant meaning beyond the schema definition.

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 action (delete) and the resource (relations from the knowledge graph). It specifies that it handles multiple relations, distinguishing it from single-relation operations or other entity operations like delete_entities.

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?

No explicit guidance on when to use versus alternatives. The description implies usage for deleting relations but does not mention when not to use (e.g., for single relation deletion or bulk deletion vs iterative calls). Alternatives like create_relations exist but are not referenced.

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