batchAddEntities

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

The description reveals that the tool creates entities (write operation, consistent with annotations) and returns entity IDs. However, it lacks details on error handling, partial failures, or limits. Annotations provide readOnlyHint=false, but no further behavioral traits are disclosed.

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, front-loaded with the action, and contains no extraneous information. It efficiently conveys the core functionality.

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 no output schema, so the description's mention of returning 'all entityIds' is helpful. However, it could be more complete by noting ordering, validation, or partial success behavior. For the complexity level, it is mostly adequate.

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 description adds minimal value beyond what the schema already provides. It mentions return value but does not elaborate on parameter meaning or syntax.

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's purpose: to batch add multiple entities of various types in one call, and it returns entity IDs. This distinguishes it from sibling tools like addMarker, addModel, etc., which handle single 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 use for batch operations but does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or context like performance implications.

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