Place scene item

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

All annotations are false, so the description carries full burden. It states it 'sets' properties, implying mutation, but does not disclose whether it is a partial update (only provided params changed) or a full reset of unspecified properties. It also doesn't mention potential side effects or error conditions. This is a significant gap for a mutating 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?

Two sentences, front-loaded with the purpose and then a key clarification about width/height and fit modes. No redundant information, every word earns its place. Very efficient.

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?

With 15 parameters and 13% schema coverage, the description is far from complete. It does not mention that sceneItemId is required, does not explain units or defaults for most parameters, and does not clarify whether the operation is incremental or overwriting. The description is insufficient for a complex tool like this.

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 only 13%, so the description must compensate. It adds meaning for 'width+height use OBS bounds' and explains the 'fit' enum values (contain, cover, stretch). However, it does not clarify semantics for scale, rotation, crop, or how to specify the scene (sceneId/sceneName). It provides partial added value but leaves many parameters unexplained.

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 verb 'Set' and the resource 'scene item', listing the specific transform properties (position, size, scale, rotation, crop). This distinguishes it from sibling tools like scene_item_transform_get (get) and scene_item_remove (remove). No ambiguity about what it does.

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 this tool is for modifying transform properties, and the sibling list shows scene_item_transform_get for reading. However, it does not explicitly state when to use this over alternatives, nor does it mention prerequisites or exclusions. The usage context is implied but not explicitly stated.

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