Create Relations

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

The description contradicts the annotation openWorldHint=false by stating 'Missing endpoint entities are created automatically.' This is an open-world behavior, directly conflicting with the closed-world annotation. Therefore, score is 1 per contradiction rule.

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 three concise sentences, each adding distinct value: main purpose, formatting rule, and auto-creation behavior. No redundant information; it's front-loaded with the primary action.

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?

The description covers the main usage and key behavior (auto-creation). An output schema exists, so return values are presumably defined. However, the contradiction with openWorldHint could confuse an agent; also, edge cases like partial failures are not addressed. But given the moderate complexity, it's mostly complete.

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 description adds meaning beyond the schema: 'Relations should be in active voice' specifies the format for relationType, and 'Missing endpoint entities are created automatically' clarifies that from and to can reference non-existent entities, which will be created. This complements the 50% schema coverage.

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 tool's function: 'Create multiple new relations between entities.' This distinguishes it from sibling tools like create_entities (creates entities) and delete_relations (deletes relations). The additional details about active voice and automatic endpoint creation further clarify behavior.

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 clear context: it is for creating multiple relations, with guidance that relations should be in active voice. It does not explicitly mention alternatives or when-not-to-use, but the naming and sibling set make the purpose clear. The lack of explicit exclusion is acceptable given the straightforward domain.

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