Transform Selection

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

Annotations indicate it's a mutating operation; the description adds the order of application and details about each parameter. It does not disclose that changes can be undone or selection is preserved, but that is standard. No annotation contradictions.

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 brief paragraphs: first for purpose, second for parameters. No wasted words; every sentence adds 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?

For a tool with 6 optional parameters and no output schema, the description covers all aspects needed to use it correctly: purpose, parameter format, order, and conditional usage.

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 100% (all 6 parameters documented). The description adds value by clarifying the application order and explaining that scale_x/scale_y are used only when 'scale' is omitted, and that dy positive = down.

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 action ('Move, rotate and/or scale') and the resource ('currently selected objects'). It distinguishes from sibling tools like illustrator_align_selection by focusing on arbitrary transforms.

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 specifies the order of operations (move -> rotate -> scale) and that all arguments are optional, but does not explicitly contrast with sibling tools. The context among siblings makes the usage clear enough.

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