Graph Relate

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

Discloses idempotence (re-assertion boosts weight) and atomicity of batch mode. The annotation confirms idempotentHint, so description adds context beyond that.

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 sentences, each with distinct purpose: core function, single mode, batch mode + idempotence. No fluff, 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?

Despite 13 parameters and nested objects, the description covers key behaviors (mode selection, idempotence, atomicity) and the schema is well-documented. No output schema but tool likely returns success; sufficient for agent to use.

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 baseline is 3. Description adds value by explaining how parameters relate to modes (single vs batch) and the effect of weight boosting, going beyond raw schema descriptions.

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 precisely states the tool creates or strengthens relationships between entities, distinguishes it from siblings like graph_delete or graph_merge, and clearly separates single and batch modes.

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?

Explicitly guides when to use single mode (one fact) vs batch mode (transcript/document extraction), and mentions batch is atomic to prevent dangling nodes. Does not list alternatives but provides solid usage context.

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