batch_create

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

With no annotations, the description must carry the behavioral disclosure burden. It only states that multiple entities are created, but gives no details about side effects, prerequisites (e.g., project must exist), error handling, or behavior of the autoIncrement feature. This is minimal transparency.

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, well-structured sentence that communicates the action (create), scope (multiple), and supported entity types. It is front-loaded with the verb and contains no unnecessary words.

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?

This tool has no output schema and no annotations, and the description is only one sentence. It lacks important context such as when to use batch_create over single create tools, behavioral expectations, and any notes about efficiency or limitations. The description is incomplete for a tool of this complexity.

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 80% and each parameter has a description in the input schema, so the baseline is 3. The tool description adds no additional meaning beyond listing entity types, which is already covered by the entityType enum in the schema.

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 multiple entities at once and lists specific entity types (maps, events, items, skills, armor, weapons). This distinguishes it from sibling tools like create_map and create_event, which focus on 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 phrase 'at once' implies a batch use case, but the description does not explicitly say when to use this tool instead of the single-entity creation tools. No alternatives or exclusions are mentioned, so the guidance is only implicit.

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