create_entity

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It reveals that this is a mutating operation and warns about duplicate risk, but it does not explain what happens if a duplicate is attempted, whether the operation is idempotent, or what side effects occur beyond creation.

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?

Two compact, focused sentences with no filler. The core action is front-loaded and the essential safety instruction follows immediately with no wasted wording.

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?

The description is adequate for a simple create operation given full schema coverage and an output schema, but it is incomplete for a mutation with no annotations. It leaves unclear how duplicate entities are handled and what error or response behavior to expect, which an agent would need to invoke the tool safely.

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 input schema already documents both parameters, including uniqueness for entity_name and an example for entity_data. The description reinforces the uniqueness concern but does not add new parameter-level meaning.

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 specific verb ('Create'), a clear resource ('a new entity in the knowledge graph'), and a distinct scope that separates it from sibling tools like create_relation or create_document. An agent can tell exactly what action this tool performs.

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?

Explicitly instructs the agent to call check_entity_exists first to avoid unintended duplicates, which is a concrete and valuable usage guideline. It does not state when not to use this tool or mention alternatives like edit_entity, so it misses the bar for a full 5.

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