batch_add_elements

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

With no annotations provided, the description carries the full burden. It discloses key behavior: 'performs only one file read and one file write regardless of how many elements are added' and mentions automatic white background on edge labels. However, it does not specify whether elements are appended to or replace existing content, file-creation behavior, or error handling, leaving notable 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 front-loaded with a clear purpose and efficiency statement, followed by a clearly labeled 'LAYOUT BEST PRACTICES' section. It is longer than minimal, but each sentence provides actionable guidance for layout quality, justifying the length.

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 provides good context for purpose and usage, but for a complex nested-object tool with no output schema, it omits critical details: whether edges can reference nodes created in the same batch, how existing diagram content is handled (append vs overwrite), and what the return value indicates (success/failure). These gaps make it incomplete for fully reliable 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 the baseline is 3. The description adds valuable guidance beyond the schema, such as 'Space nodes at least 200px apart horizontally and 150px vertically', 'Use "curved" edgeStyle when multiple edges connect the same nodes', and 'Use exitPoint/entryPoint to separate parallel edges.' These best practices help an agent choose appropriate parameter values, exceeding what the schema alone provides.

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: 'Add multiple nodes and edges to a draw.io diagram in a single operation.' It also distinguishes this from sibling tools add_node/add_edge by highlighting efficiency and batching, making the purpose unambiguous.

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 explicitly advises when to use this tool: 'Much more efficient than calling add_node/add_edge individually' and 'Use this for building entire diagrams or adding multiple components at once.' It names alternatives and provides a clear use case, satisfying the when-to-use criterion.

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