KG Add Entities Batch

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

The description discloses key behaviors: batch size limit (500), transactional grouping, return of created/duplicate counts and per-row errors, and the ability to retrieve an ids array via verbose response format. Annotations indicate idempotent and not destructive, which aligns with the description. No contradiction.

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 sentences convey all essential information: batch size, transactional nature, return values, and verbose option. No filler or redundancy. 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?

The description covers the core operation adequately given the tool's complexity. With an output schema present, return value explanation is not needed. However, it omits detail on per-row error format and does not explain the entities structure, which could be needed. Still, for a batch creation tool, it is mostly complete.

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?

With 0% schema description coverage, the description carries the burden. It only covers the 'response_format' parameter by noting the verbose option. The main 'entities' parameter (with nested fields) is not described at all—no explanation of name, type, properties, or memory_id. This is a significant gap.

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 tool creates entities in batch (up to 500) with transactional semantics. It distinguishes from the single-entity sibling by its batch nature and explicitly mentions return values (counts, errors, optional ids). The verb 'Create' and resource 'entities batch' are specific and unambiguous.

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 batch creation without explicitly contrasting with alternatives. The phrase 'single transactional batch' suggests atomicity and batching, which helps the agent decide when to use this vs. the single-entity add tool. However, it lacks explicit when-not or alternative mentions.

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