create_entity

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

Apart from readOnlyHint=false, there are no behavioral annotations, and the description does not disclose side effects, permission requirements, ID generation, uniqueness behavior, or what happens on duplicate names. For a mutation tool, the description alone carries the burden of behavioral disclosure and does not satisfy it.

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, front-loaded sentence contains no filler and immediately communicates the operation. It is appropriately sized for the straightforward purpose it states.

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 tool has six parameters, nested value objects, and no output schema, yet the description only states the action. It does not mention returned entity/ID, required type setup, or how relation/values structures behave, leaving too much context for the agent to infer.

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 every parameter is already described in the input schema; the description adds no additional parameter semantics. Baseline 3 applies because the schema carries the parameter documentation burden.

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 a specific action ('Create') and object ('an entity instance in the knowledge graph'), making the tool's core purpose immediately clear. It distinguishes from nearby siblings such as create_type, create_property, create_relation, and create_image by naming the entity instance resource, though it does not explicitly name those alternatives.

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 guidance is given for when to choose this tool over alternatives such as update_entity, add_values_to_entity, or create_type. The description only states what the tool does, not when it should be invoked or whether prerequisites like existing type/property/relation IDs are required.

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