create_relationships

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

The description states 'between existing entities' implying a requirement, but lacks details on error handling (e.g., partial failures), duplicate checking, or authentication needs. No annotations are provided to offset these gaps.

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, which is concise, but it is too short to cover essential details for a complex batch operation. It earns its place but leaves significant gaps.

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 complexity (batch creation, many relationship types, multiple parameters, no output schema), the description is severely incomplete. It does not explain return values, error states, or constraints beyond existence.

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?

With 0% schema description coverage, the description adds no meaning to parameters. The array 'relationships' and its fields, 'source_id', and 'user_id' are not explained beyond their names.

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 creates multiple typed relationships in a batch, distinguishing it from the sibling tool 'create_relationship' which likely handles single relationships. The verb 'create' and resource 'typed relationships' are specific.

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 on when to use this tool vs 'create_relationship' or other tools. The description does not mention prerequisites like entity existence, which is critical.

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