place_cell

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

With no annotations, the description must cover behavioral traits. It explains orientation format, array parameters (dx, dy, nx, ny), and coordinate units. However, it omits details on return value, side effects, or required state (e.g., active cell existence). The explanation is partial.

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 very concise: two sentences plus a line for specifics. The purpose is front-loaded, and every sentence adds value. No redundant information.

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?

Given the tool's complexity (9 parameters, array support, orientation) and lack of annotations, the description covers the main operation and key parameters. However, it does not explain output, error handling, or default behaviors. The existence of an output schema may compensate, but the description alone is incomplete.

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 0%, so the description must compensate. It explains orient, dx, and dy, but fails to describe x, y, nx, ny, mag, and cell in detail. The phrase 'Coordinates in um.' loosely applies to x/y but is not explicit. Overall, most parameters lack meaningful explanation.

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's function: placing an instance or array of a cell into the active cell. It mentions orientation options and coordinate units, making the purpose specific and distinct from sibling tools like create_cell or use_cell.

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 does not provide guidance on when to use this tool versus alternatives. It lacks explicit context, prerequisites, or exclusion criteria, making it weak for helping an agent decide between siblings.

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