create_entities

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

No annotations are provided, so the description carries full burden. It states 'Create new entities' which implies a write/mutation operation, but doesn't disclose behavioral traits like permissions needed, whether it's idempotent, rate limits, or what happens on failure. The mention of 'optional embeddings' hints at functionality but lacks operational context.

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, efficient sentence with zero waste. It's front-loaded with the core action and resource, and every word ('new entities', 'observations', 'optional embeddings') adds value. No extraneous information or repetition.

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?

Given no annotations, no output schema, and a single but complex parameter (nested array of objects), the description is incomplete. It doesn't explain return values, error handling, or the full scope of entity creation (e.g., validation rules, uniqueness constraints). For a mutation tool with rich nested data, more context is needed.

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%, so the description must compensate. It adds meaning by specifying that entities include 'observations and optional embeddings', which clarifies the purpose of the 'entities' array parameter beyond the schema's structural definition. However, it doesn't detail all nested fields like 'entityType' or 'name', leaving some semantics uncovered.

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 the verb 'Create' and the resource 'new entities', specifying they include 'observations and optional embeddings'. It distinguishes from siblings like delete_entity (deletion) and read_graph/search_nodes (read operations), though not explicitly named. The purpose is specific but could more directly contrast with create_relations.

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 on when to use this tool versus alternatives is provided. It doesn't mention prerequisites, when not to use it, or compare with siblings like create_relations (for relationships) or search_nodes (for finding existing entities). The description implies usage for entity creation but offers no contextual boundaries.

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