Set Scene Item Transform

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

The description adds the scope of mutation (position, rotation, scale, or crop), which the annotations do not state, and it is consistent with idempotentHint and destructiveHint. However, it does not disclose meaningful behavioral details such as partial-update semantics, units/coordinate conventions, or how sceneItemTransform interacts with the scalar fields.

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 redundant wording. It is appropriately brief, though it sacrifices some behavioral and usage context for brevity.

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?

The schema covers all parameter meanings and the annotations cover basic safety traits, making the tool usable, but the description is minimal for a 14-parameter setter with no output schema. It lacks guidance on partial updates, unit conventions, and the relationship between sceneItemTransform and individual transform fields.

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?

All 14 parameters already have descriptions in the schema, providing 100% coverage, so the baseline is 3. The description merely summarizes the same properties and does not add any new meaning beyond the schema.

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 ('set') and identifies the resource ('scene item') plus the concrete properties affected (position, rotation, scale, crop), which clearly distinguishes it from scene-item getters and other scene-item setters. It stops short of a 5 because it does not explicitly name related alternatives like obs-get-scene-item-transform.

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?

No explicit guidance is provided about when to use this tool versus sibling tools, such as obs-get-scene-item-transform or other scene-item setters. The intended use is only implied by the title and description, with no exclusions or alternative recommendations.

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