Batch Create Entities

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

Annotations only declare readOnlyHint=false, so the description must carry behavioral weight. It does add performance intent and the batch-composition behavior vs cad_batch, but it does not disclose failure semantics, atomicity, or limits on batch size. This is useful but not rich enough to exceed a mid score.

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?

Every part earns its place: purpose, required structure, example, and the comparative guidance with cad_batch. It is compact, front-loaded with purpose, and the example is directly useful rather than filler.

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 single-parameter tool with an output schema, the description covers the essential call-shape, example, and relationship to cad_batch. It does not mention edge cases like invalid entity types or partial failures, but those are secondary given the schema richness and sibling context.

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 baseline is 3. The description goes beyond schema by giving a concrete two-entity example showing exact dict shapes for line and circle, and by emphasizing the required 'type' key in a direct, actionable way.

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 opens with a clear verb-resource pair: 'Create multiple entities in a single call.' It explicitly positions this against cad_batch and the single-entity create tools, making its role in the sibling set apparent.

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 gives explicit when-to-use guidance: use for better performance, use for many entities of the same kind, and use cad_batch when calls differ, must be ordered, or must feed each other. It also notes this tool can be a step inside cad_batch.

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