create_cell

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

Discloses that subsequent draw calls go into this cell and that use_cell returns to top. Lacks detail on whether existing cells are selected or new cells created, but overall covers key behaviors.

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?

Two concise sentences with no wasted words. Front-loaded with purpose and immediate usage context.

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?

Adequate for a simple tool with one parameter. Does not explain return value or error conditions, but the workflow context is well covered.

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 only parameter 'name' is explained by 'create (or select) a cell', adding meaning beyond the schema. Could be more explicit but sufficient.

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?

Description clearly states the tool creates or selects a cell and makes it the active drawing target. It distinguishes from sibling drawing primitives by specifying it sets the context for subsequent shapes.

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?

Explicitly describes workflow: use this to build a library cell, then use_cell and place_cell. Provides clear instructions on when and how to use, including returning to top cell.

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