streamlabs_center_scene_item

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

With no annotations, the description carries full responsibility for disclosing behavioral traits. It merely states the action without mentioning side effects (e.g., whether it overrides existing position, preserves scale, or affects locked items). It also fails to clarify why three identifiers are needed or how they relate. This is minimal for a mutation tool.

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 sentence that is immediately clear and front-loaded with the action verb. Every word is purposeful, and there is no redundant content.

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 mutation tool with three required parameters and no annotations or output schema, this description is inadequate. It does not explain what 'center' means operationally, why all three parameters are necessary, or what the expected outcome is. The tool is too thin for an agent to invoke confidently.

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 provides no explanations for sceneId, sceneItemId, or sourceId. The purpose of sourceId is particularly ambiguous—does it identify the source attached to the scene item? The description adds zero value beyond the schema's bare property 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 ('Center') and the resource ('a scene item on the canvas'). It is specific enough to distinguish this tool from sibling tools like set_scene_item_transform or fit_scene_item_to_screen, as centering is a unique operation.

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 guidance is provided on when to use this tool versus alternatives, such as when to use fit_scene_item_to_screen or set_scene_item_scale. The description gives no context about scenarios that favor centering, nor does it exclude other tools. This leaves the agent without decision support.

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