Set Scene Name

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

Annotations already communicate the important behavioral traits: readOnlyHint=false, idempotentHint=true, and destructiveHint=false. The description adds no further behavioral context, such as effects on scene references or return behavior, but it is consistent with the annotations.

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 front-loaded sentence, 'Rename an OBS scene,' with no filler or redundancy. Every word contributes to the meaning.

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, and annotations plus full schema coverage cover much of the needed context. However, the description omits how to identify the target scene and does not clarify why only newSceneName is required, leaving a meaningful gap for an agent trying to invoke the tool correctly.

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 descriptions cover 100% of parameters and provide basic definitions for sceneName, sceneUuid, canvasUuid, and newSceneName. The description itself adds no parameter-level meaning, so the baseline score of 3 applies; it also does not clarify that at least one scene identifier should be supplied even though only newSceneName is marked required.

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?

Description uses the specific verb 'Rename' and the resource 'OBS scene', making the operation unambiguous. It also distinguishes this tool from sibling scene tools like obs-create-scene, obs-remove-scene, and obs-set-current-scene.

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 gives no explicit guidance about when to use this tool versus alternatives, nor does it mention prerequisites such as needing an existing scene identifier. The only usage clue is the verb in the description, so an agent must infer context from the tool name alone.

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