create_entity

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only says 'Create' without explaining side effects, duplicate handling, whether existing entities are updated, or whether any validation occurs. An agent cannot know if creating an entity with an existing name fails, overwrites, or creates a duplicate.

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 a single sentence with no filler. It front-loads the core action ('Create an entity in the knowledge graph') and uses the parenthetical examples efficiently, earning every word.

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 creation tool with a fully documented schema, the description is adequate to make a correct call. However, the absence of annotations and output schema means return values, duplicate behavior, and required relationship to existing entities are not disclosed, leaving some operational context missing.

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 coverage is 100%, so the baseline is met and the schema already documents all five parameters. The description adds examples like 'technique, actor, tool, detection', but these mostly mirror the schema's type enum and do not enrich parameter meaning beyond it.

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 a specific verb and resource: 'Create an entity in the knowledge graph', with concrete examples of entity types. It naturally distinguishes itself from sibling tools like create_relation and search_entities, so an agent can tell what this tool does at a glance.

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 explicit guidance about when to use this tool versus alternatives such as create_relation or search_entities. The knowledge graph context and examples imply a use case, but there is no stated condition, prerequisite, or exclusion, leaving the agent to infer when creation is appropriate.

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