Create Entities

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so the safety profile is partly covered. The description adds nothing about what happens when an entity name already exists, whether the batch is atomic, or whether duplicates are merged — the key behavioral questions for a non-idempotent write tool.

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?

A single compact sentence, front-loaded with the verb and resource. Nothing is wasted, but there is also very little content to be structured.

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?

An output schema exists, so return values need not be described, and annotations carry the safety hints. Still, for a non-idempotent batch-creation tool the description omits duplicate-handling, batch failure semantics, and prerequisite context, leaving meaningful gaps.

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 0% at the top level, but the nested item schema documents name, entityType, and observations, and the word 'multiple' signals the batch/array shape. The description adds no format, uniqueness, or required-field detail beyond that, so it neither compensates nor misleads.

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?

States a clear verb ('Create'), resource ('entities'), and a scope qualifier ('multiple new ... in the knowledge graph'). It separates itself from create_relations and add_observations by naming entities, though it never explicitly contrasts with the sibling that appends 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?

No when-to-use guidance and no alternatives named, despite siblings add_observations, create_relations, and delete_entities being obvious candidates for confusion. The agent must infer that this tool is for brand-new entities rather than extending existing ones.

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