streamlabs_set_scene_item_transform

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

With no annotations, the description discloses a critical behavioral trait: only provided fields are changed, leaving others untouched. This patch-style partial update is not apparent from the schema alone, as the schema only marks fields as optional without stating that omitted ones are preserved.

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 two short sentences, front-loaded with the action, and every word earns its place. The second sentence provides an essential usage note without any filler.

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 7 parameters and nested objects, the description covers the core action and partial-update behavior but omits details like coordinate/unit conventions and when to choose this over more specific transform tools. The absence of annotations and output schema increases the burden, so more context would improve completeness.

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%, and the description only lists property names without explaining units, coordinate systems, or value meanings. It does add the partial-update semantics, but it fails to compensate for the missing schema descriptions, leaving parameter meaning vague.

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 identifies the tool as setting transform properties (position, scale, crop, rotation) on a scene item, using the specific verb 'Set'. It directly distinguishes itself from single-purpose siblings like set_scene_item_scale and rotate_scene_item by mentioning the full set of transform fields.

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 phrase 'and/or rotation' and 'Only pass the fields you want to change' imply the tool is for partial updates and general property setting. However, it does not explicitly reference alternatives or state when to prefer this over single-purpose sibling tools, so guidance is implied rather than explicit.

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