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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false. The description adds useful behavioral context: the 500-call limit, the use of Neo4j UNWIND for high performance, and the requirement that entity_id be unique. However, it does not explain failure behavior, partial writes, or return format, so transparency is adequate but not rich.

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 front-loaded with the primary action and limit in the first sentence. The use case and parameter requirements are concise. The example is somewhat long but necessary for showing the nested node structure. No wasteful filler.

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?

For a bulk write tool with no output schema, the description covers the core behavior, limits, example usage, and parameter requirements. It lacks explicit error-handling or idempotency notes, but annotations cover idempotency, and the example provides practical context. Overall, the description is sufficiently complete for safe invocation.

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 description coverage is 100%, so the baseline is 3. The description adds value beyond the schema by clarifying the internal structure of the 'nodes' parameter ('Each node needs: entity_id (unique string) and data (properties dict)') and providing a concrete example with 'entity_type' and 'nodes' array. This helps the agent construct valid input.

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 'Create multiple nodes at once' with a specific resource (graph nodes) and a scope limit ('up to 500 per call'). It distinguishes itself from the singular sibling tool 'create_graph_node' by emphasizing the bulk nature, and the example reinforces the purpose.

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?

It explicitly positions the tool for knowledge graph population: 'Essential for knowledge graph population — create hundreds of entities from a single book chapter or article.' This indicates when to use it, though it does not explicitly mention alternatives or when not to use it (e.g., for single-node creation).

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