add_nodes

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Add multiple new nodes' implies a write/mutation operation, the description doesn't address important behavioral aspects like: what permissions are required, whether nodes must be unique, what happens on conflicts, whether the operation is atomic, or what the response looks like. For a mutation tool with zero annotation coverage, this is a significant gap.

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 extremely concise - a single sentence with zero wasted words. It's front-loaded with the core purpose and contains no unnecessary information. This is an excellent example of efficient communication.

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 mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't address the behavioral aspects needed for safe use (permissions, error conditions, response format) or provide context about how this tool relates to the many specialized sibling tools. The 100% schema coverage helps with parameters, but other critical context is missing.

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 schema already fully documents the single 'nodes' parameter and its nested structure. The description adds no additional parameter semantics beyond what's in the schema - it doesn't explain what constitutes a valid node, provide examples, or clarify the relationship between node properties. Baseline 3 is appropriate when the schema does the heavy lifting.

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 action ('Add multiple new nodes') and the resource ('in the knowledge graph'), which provides a specific verb+resource combination. However, it doesn't distinguish this tool from sibling tools like 'add_artifact' or 'add_location' that also add specific types of entities to what appears to be the same knowledge graph system.

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 provides no guidance on when to use this tool versus alternatives. With many sibling tools that add specific entity types (artifact, currency, location, etc.), there's no indication whether 'add_nodes' is a general-purpose tool for arbitrary nodes or whether it has specific use cases compared to the more specialized add_* tools.

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