streamlabs_reset_scene_item_transform

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the operation but does not mention that it overwrites existing transform values, potential side effects, permission requirements, or error conditions. This is a mutation with untold consequences.

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 concise sentence that immediately communicates the core action. It is well-structured and avoids clutter, though it could have used the space to clarify parameters without losing conciseness.

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 tool is simple, but with three required parameters, no annotations, and no output schema, the description should clarify how the parameters relate and what 'default' means. It notably omits any explanation of sourceId, which is puzzling alongside sceneItemId. The description is not complete enough for reliable invocation.

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 0% and the description does not explain any of the three parameters (sceneId, sceneItemId, sourceId). The parameter names are self-descriptive but the role of sourceId is unclear, and there is no indication of which scene item is targeted. The description adds no value beyond the schema's field names.

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 ('Reset') and the resource ('a scene item's position, scale, and rotation'), and specifies 'to default', which distinguishes it from setter tools like streamlabs_set_scene_item_transform. This is a specific and unambiguous purpose.

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 implies the tool should be used when reverting a scene item's transform to defaults, but it provides no explicit 'when to use' vs 'when not to use' guidance or references to alternatives like set_scene_item_transform. The context is clear enough for a simple reset operation.

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