batch_create

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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions performance improvement but omits critical details like execution order (sequential), atomicity, error handling (partial failure or rollback), and response format. These gaps hinder an agent's ability to use the tool correctly.

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 consists of two concise sentences, front-loaded with the core purpose and a key benefit. Every word is informative, and there is no unnecessary text.

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 batch tool with a nested array parameter and no output schema, the description lacks completeness. It does not explain the params object format, error behavior, or what the tool returns. Additionally, it does not guide the agent on how to construct operations using sibling command names.

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?

The schema coverage is 100%, and the schema includes a description for the 'operations' parameter. The tool description adds no extra meaning beyond the schema, merely restating the concept of executing multiple commands. Baseline 3 is appropriate as the schema does the heavy lifting.

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 executes multiple Figma commands in a single batch, improving performance for bulk operations. It uses a specific verb ('execute') and resource ('multiple Figma commands'), and distinguishes itself from sibling tools that perform individual commands.

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 indicates use for bulk operations (e.g., creating many icons or setting up variables) to improve performance. It implies this tool is preferable over individual calls for such tasks, but does not explicitly state when not to use it or provide alternative tools.

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