array_rect

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

With no annotations provided, the description carries the full burden. It discloses the special 'selection' value for handles, but does not mention whether the original entities are copied or moved, how rows/cols spacings are measured, or behavior on invalid input.

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 two short sentences, front-loaded with the tool's main purpose. There is no fluff; every word contributes to understanding.

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 moderate complexity and no annotations, the description is minimal. It does not explain key behavioral aspects like whether arraying preserves layers, how selection is captured, or error scenarios. The output schema exists but does not cover behavioral 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?

The description adds meaning to handles by explaining the 'selection' special value, and the concept of rows x cols with spacings maps to related parameters. However, with 0% schema coverage, it does not fully explain units, ordering, or exact semantics for row_spacing and col_spacing.

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 creates a rectangular array of entities with rows, columns, and spacings. It distinguishes itself from the sibling array_polar by specifying 'rectangular', though it lacks an explicit verb like 'creates'.

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 provides no guidance on when to use this tool versus alternatives like array_polar. It only hints at using the GUI selection via handles=['selection'], but does not explain typical use cases, prerequisites, or exclusions.

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