Create Entities

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

The description states that entities with an existing name are ignored, which implies idempotent behavior (repeated calls with the same entities have no additional effect). However, the annotations set idempotentHint to false, directly contradicting this implication. Per the rubric, this is an annotation contradiction requiring a score of 1.

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, consisting of two short sentences. It front-loads the purpose and adds the key behavioral trait (ignoring existing names) without extraneous information. Every word earns its place.

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 simple batch creation tool, the description covers the core purpose and the most critical edge case (duplicate names). The schema provides details on parameters and the output schema exists (though not shown), so return values need not be described. However, the idempotency contradiction weakens overall completeness, and there is no mention of partial failures or namespace defaults, though those are partly addressed by schema.

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 50% description coverage: the 'namespace' parameter is well-described, but the 'entities' array property lacks a top-level description. The tool description adds no further parameter semantics—it merely repeats the word 'entities' without explaining the structure or namespace behavior, leaving the agent to rely entirely on the incomplete 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 clearly states the tool creates multiple new entities in the knowledge graph, using a specific verb ('Create') and resource ('entities'). It is distinct from sibling tools like create_relations, which handle relations, and add_observations, which add observations to existing entities.

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 this tool is for adding new entities, and the behavior of ignoring existing names is a useful context cue. It does not explicitly state alternatives or when-not-to-use, but the sibling tool names provide enough situational awareness for an agent to differentiate.

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