set_scene_item_transform

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

No annotations are provided, so the description must disclose behavior. It states the tool moves/scales and gives a partial update behavior example, but does not cover coordinate system, value limits, or error conditions, leaving significant gaps for safe usage.

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 exceptionally concise: two sentences that front-load the purpose and add a key behavioral nuance with an example. Every word serves a purpose with no redundancy.

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 7 parameters, no annotations, and no output schema, the description provides only the essential intent and a partial-update behavior. It omits coordinate semantics, default behavior, dry_run explanation, and potential pitfalls, resulting in an adequate but incomplete picture.

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?

With 0% schema description coverage, the description adds meaning for scale_x/scale_y via the example and clarifies that only supplied fields change. However, it fails to explain x, y, dry_run, or the required scene parameter, relying on assumed context.

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 moves or scales a scene item, referencing item_id from list_scene_items, which distinguishes it from related tools like set_scene_item_visibility or get_scene_item_transform. The example with scale_x/scale_y reinforces the specific action.

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 explains that only supplied fields change, implying selective updates, and references deriving item_id from list_scene_items. However, it lacks explicit guidance on when to use versus alternatives or prerequisites beyond the implicit item_id.

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