array

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation risk is known. The description adds useful context by saying copies are merged into one mesh (i.e., the result is a single combined object rather than separate instances), but it stays silent on whether the source object is consumed or preserved, which is a material detail for a destructive operation.

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 short sentences with the core action front-loaded and no filler. The trailing example list is efficient but reads as a verbless fragment, which is mildly cryptic rather than wasteful.

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?

With 5 parameters, 0% schema description coverage, and no output schema, the description leaves significant gaps for an agent: keep_source behavior, the role of `name`, and the fate of the source object are never addressed. The core operation is clear, but not enough is disclosed to call this tool correctly.

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 0%, so the description must carry the load, and it only partially does: it defines `count` (times to repeat) and `offset` (world vector, step in metres). The `object`, `name`, and especially `keep_source` parameters — the latter directly tied to the destructive annotation — receive no explanation anywhere.

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 gives a specific verb+resource ('repeat an object count times ... merge copies into one mesh') that an agent can act on, and the 'along the world vector offset' phrasing implicitly separates it from the sibling radial_array. It does not explicitly name radial_array/duplicate/mirror, so sibling differentiation is inferential rather than stated.

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?

Usage is only implied via the trailing examples ('Fences, stairs, windows, planks, teeth'), which sketch realistic use cases but give no when-to-use rule or comparison to radial_array, duplicate, or mirror. There is no statement of when NOT to use it or what alternative to pick for radial/circular repetition.

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