item_set_transform

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

No annotations are present, so the description carries the full behavioral disclosure burden. It successfully reveals the partial-update semantics (null parameters are ignored, existing values preserved), which is key behavioral context beyond the schema. It does not discuss error cases or permissions, but for a setter tool this is a meaningful and sufficient disclosure.

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 only two sentences, with the main action in the first sentence and the crucial qualifier in the second. Every word adds information, and the structure is front-loaded with the purpose.

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 10-parameter schema and no annotations, the description plus schema covers the action, parameter meanings, and update behavior. However, the role of track_type and track_index in identifying the target item is not explained, which is a small but relevant gap. Since an output schema exists, not describing return values is acceptable.

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 100%, giving a baseline of 3. The description adds valuable parameter-level semantics by explicitly stating that only non-None parameters are applied, clarifying that null means 'leave unchanged' rather than 'clear the value.' It also groups the main transform parameters, reinforcing what they collectively affect.

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 uses a specific verb with a clear resource and property list: 'Set transform properties (zoom, position, rotation, anchor) on an item.' This directly distinguishes it from sibling tools like item_set_property, item_set_crop, or item_set_composite.

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 clear usage guidance by stating 'Only non-None parameters are applied; the rest remain unchanged,' which tells the agent how to use optional parameters. It implies this tool is for transform updates, but it does not explicitly list when not to use it or name alternatives.

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