Batch Create Nodes

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

Annotations only indicate a non-read-only, non-destructive operation. The description adds valuable behavioral context: atomicity (all-or-nothing transaction) and automatic FTS5 search index synchronization. This goes beyond the minimal annotation hints, although it does not detail error handling or permission requirements.

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, focused sentence that leads with the core action ('Atomically create multiple nodes') and adds one relevant detail (FTS5 synchronization). No filler or redundancy.

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 moderate complexity (array input, atomicity), the description, combined with a fully-described schema, is sufficient for an agent to select and invoke the tool. It captures the essential behavior and constraints, though it does not mention return values or edge cases, which is acceptable given no output schema.

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?

Input schema has 100% description coverage for both parameters (nodes and project), so the schema already explains the parameters. The description does not add further parameter-specific details, keeping this at the baseline score of 3.

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 'creates multiple nodes' atomically, with a specific resource (nodes) and action. It distinguishes from sibling tools like add_node (single creation) and batch_update (updates, not creates) by emphasizing 'multiple' and 'single transaction'.

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 implies when to use: when you need to create several nodes atomically and ensure FTS5 index synchronization. It does not explicitly name alternatives or state when not to use, but the context of 'multiple' and 'single transaction' is a clear usage signal compared to single-node creation tools.

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