delete_relations

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

The description only states 'delete', implying a destructive action, but with no annotations to reinforce safety. It does not disclose reversibility, cascading effects, required permissions, or any side effects, failing to meet the burden for an unannotated tool.

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 a single sentence, front-loaded with the action and object. It contains no fluff, and every word is necessary to convey 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?

Given the simplicity of the tool (one parameter, no output schema, no annotations), the description is minimal but barely adequate. It lacks any behavioral context like return values or confirmation, leaving some gaps for an agent.

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 100%, with all properties described in the schema. The description adds no additional meaning beyond what the schema already provides, such as clarifying the 'relations' array or its items. Baseline 3 is appropriate as no extra value is added.

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 it deletes multiple relations, using a specific verb and resource. It distinguishes from sibling tools like 'delete_entities' or 'delete_observations' by specifying 'relations', though it does not further differentiate from 'create_relations' or 'update_relation' which is implied by the action.

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 guidance is provided on when to use this tool versus alternatives. There are no explicit context hints, usage caveats, or mentions of when not to use it, leaving the agent without decision support.

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