create_entities

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

With no annotations, the description carries the full burden for behavioral disclosure. It only states required fields and the creation action, but does not mention potential side effects, partial success, conflicts with existing entities, permissions, or validation behavior. This leaves significant gaps about what actually happens when the tool runs.

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 two sentences, front-loaded with the tool's purpose, and then lists the required structure. No superfluous words or repetition of schema properties. It is efficiently organized and easy to parse.

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 creation tool, the description covers its main purpose and the required input structure. An output schema exists, so return values are not the description's responsibility. However, it does not mention error handling, atomicity, or constraints on values, which could be relevant for a multi-entity operation. Still, the core information is present.

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?

The input schema only defines 'entities' as an array of objects with additionalProperties true, providing zero structure. The description fills this gap by explicitly specifying each entity must have name (str), entityType (str), and observations (list[str]). This is essential, unique information not present in the schema.

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 states 'Create multiple new entities in the knowledge graph' with a specific verb ('create') and resource ('entities in the knowledge graph'). This clearly distinguishes it from sibling tools like create_relations or add_observations, which target different graph elements.

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 clearly implies the use case: you invoke this when you want to add new entities. It does not explicitly name alternatives or list when not to use, but the context is unambiguous for a creation action. This meets the 'clear context, no exclusions' standard.

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