Delete relations

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered; the description adds real semantics beyond that by explaining that unmatched relations are ignored (concrete idempotency behavior) and that the full deleted relations are returned with a summary message. Permission requirements and any cascading effects are not mentioned.

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?

Three short sentences, each carrying distinct information: the match criteria first, then the return shape, then two behavioral caveats. No filler or restatement of the title.

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 single-parameter deletion tool with an output schema and destructive/idempotent annotations, the description covers what is deleted, how matching works, behavior on misses, and the interaction with sibling delete_entities. An agent has everything needed to call it correctly.

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% and each RelationInput field is documented in the schema, so the baseline is 3. The description's mention of 'source, target, and relation type' only mirrors the schema's from/to/relationType fields without adding format or constraint detail.

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?

States a specific verb (Delete) plus resource (relations) and the matching keys (source, target, relation type), so the agent knows exactly what gets removed. It also explicitly distinguishes itself from delete_entities, which is the sibling most likely to be confused with it.

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 gives two useful routing conditions: nonexistent relations are silently ignored, and deleting an entity via delete_entities already removes its relations, implying the agent need not call this afterward. That is clear when-to-use context, though it stops short of an explicit 'use this instead of X when Y' statement.

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