create_entities

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

No annotations are provided, so the description must carry the burden. It discloses one behavioral trait: skipping duplicates by name. However, it does not mention permissions, error handling, or what happens on duplicate (overwrite vs. skip). More context on side effects is needed.

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 three concise sentences with no fluff. The first sentence states the purpose, the second details parameters, and the third provides a key behavior. Information is front-loaded 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?

Given the presence of an output schema, the description does not need to detail return values. It covers the essentials: what is needed, what is optional, and duplication behavior. It could mention the return format or success/failure signals, but the output schema likely handles that. The description is adequate for a creation tool.

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 has 0% description coverage, leaving the agent with only property names. The description compensates by listing required (name, entityType) and optional fields (observations, tags, metadata) with their types. This adds significant meaning beyond the bare schema, though the nested structure is not fully detailed.

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 it creates new entities in the knowledge graph and specifies the required and optional fields. However, it does not explicitly differentiate from sibling tools like 'create_relations' or 'add_observations', which limits its ability to help an agent choose among them.

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 usage for creating entities with specific fields, but it provides no guidance on when to use this tool versus alternatives (e.g., when to use 'create_entities' vs. 'add_observations' separately). It lacks explicit when-to-use or when-not-to-use instructions.

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