figcraft_batch

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

With no annotations, the description carries the full load, and it does disclose one meaningful trait: atomic transactional execution. It leaves out what happens on partial failure, whether commands run in order, rollback behavior, and any permission or rate constraints.

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?

A single front-loaded sentence with no filler. It could be tightened slightly but nothing is redundant.

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 one-parameter tool the description covers the core idea, and there is no output schema to explain. However, an atomic batch executor is exactly the kind of tool where failure and rollback semantics matter, and those are absent.

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 description coverage is 100%, so the schema already documents the commands array, its items, and the command/params split. The description adds no semantics of its own, such as ordering guarantees or examples of valid command names.

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 names a specific action and object: running a series of FigCraft design manipulation commands as one atomic batch. That distinguishes it from the single-operation siblings such as create_node or set_properties, though it never names a sibling or says which commands are admissible.

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?

There is no guidance on when an agent should batch operations versus calling the individual sibling tools, nor any prerequisite or exclusion stated. The word 'atomically' implies a use case (all-or-nothing multi-step edits) but the agent must infer it.

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