delete_relations

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states 'delete', which implies destructiveness, but fails to disclose permanence, error handling (e.g., what if a relation doesn't exist), or impact on associated data. The output schema exists but is not described.

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 extremely concise (6 words), front-loading the action. However, it sacrifices substance important for accurate tool selection and invocation. Every word earns its place, but the description is too terse to be fully informative.

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 tool's moderate complexity (one parameter with nested objects) and existence of an output schema, the description lacks context about return values, batch behavior, or side effects. It does not explain how the tool fits into the overall entity-relation model compared to siblings.

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%, so the baseline is 3. The description adds minimal value beyond the schema, simply restating 'specific relations' which is already implied by the required fields. No additional context is given about the format of from/to or behavior for missing relations.

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 specific relations between entities', which is a specific verb and resource. It distinguishes from siblings like create_relations and delete_entities by specifying 'relations' as the target. However, it could be more detailed about what 'specific' means, though the schema clarifies.

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 provides no guidance on when to use this tool versus alternatives like delete_entities or delete_observations. It does not mention prerequisites, when not to use it, or any conditions. This is a significant gap for agent decision-making.

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