Get Scene Transition Override

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering safety. The description adds no additional behavioral details (e.g., return format, null behavior if no override). It doesn't contradict annotations, but also doesn't provide extra context beyond what annotations already convey.

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?

A single, front-loaded sentence that states exactly what the tool does with zero redundancy. Every word adds value, and it's immediately graspable.

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 simple getter with excellent annotations, a well-documented schema, and no output schema, the description is sufficient. It doesn't explain what the returned value contains (e.g., transition name) or edge cases like missing override, but that's not critical given the tool's simplicity and the annotation coverage.

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 100% with each parameter (sceneName, sceneUuid, canvasUuid) having a clear description. The tool description adds no extra meaning beyond what the schema already documents. Baseline for high coverage is 3, and there's no additional clarification needed.

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 ('Get') and the specific resource ('the transition override configured for a scene'). It's unambiguous and distinguishes from the sibling setter (obs-set-scene-transition-override) and other transition tools like obs-get-transition-settings.

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 on when to use this tool versus alternatives. The purpose implies it's for retrieving a scene override, but no exclusions or alternative mentioning is provided. The context of being a getter and having a setter sibling makes usage inferable, but the description itself offers no guidance.

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