create_entities

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

The description discloses key behaviors ('inserts each entity if not exists', 'optionally seeds it with observations'), but lacks details on idempotency, error handling, permissions, or return values. With no annotations provided, the description carries full burden but is incomplete.

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 concise sentences with no unnecessary words. The purpose is front-loaded and every sentence adds value.

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 creation tool with no output schema and 1 parameter, the description covers the basic function. However, it lacks information on return format, duplicate handling, and error conditions, leaving some gaps for the agent.

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 100% coverage with descriptions for each field (name, entityType, observations). The description adds behavioral context ('if not exists', 'optionally seeds') that goes beyond the schema, providing meaningful additional semantics.

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 'Create entities in the knowledge graph' and explains the action: inserts each entity if not exists and optionally seeds with observations. This distinguishes it from sibling tools like add_observations which act on 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 implies usage for creating new entities but provides no explicit guidance on when to use this tool versus alternatives like add_observations or create_relations. There is no mention of prerequisites or exclusion criteria.

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