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

The annotations already establish that this is a non-readonly, non-destructive, non-idempotent operation. The description adds useful behavioral context by saying it copies shapes in place or at an offset, but it does not clarify whether originals remain selected, what new IDs or names result, or what the tool returns.

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 a single, front-loaded sentence with no wasted wording. It immediately conveys the operation and the two placement modes.

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 mutation tool with two undocumented parameters and no output schema, the description is too thin. It does not explain the required shape_ids parameter, the boolean offset semantics, or enough about the resulting copies for an agent to invoke it confidently.

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 compensate, but it only indirectly hints at the offset parameter and never explains shape_ids. It also does not clarify what offset=true means in practical terms, such as a fixed distance or direction.

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 states a specific verb and resource: copying shapes, with the option to do so in place or at an offset. It clearly describes the tool's operation, though it does not differentiate against nearby siblings such as repeat, create_shapes, or add_artboard.

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?

It offers no explicit guidance on when to use this tool versus alternatives like repeat or create_shapes. The phrase 'in place or at an offset' hints at two modes but does not explain when each is appropriate.

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