streamlabs_rename_scene

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Rename a scene' implies a mutation, but it does not mention effects on existing state, duplicate name handling, error conditions, permissions, or whether the operation is reversible. This is minimal transparency beyond the action itself.

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 with no filler, repetition, or unnecessary detail. It is appropriately sized for the simple operation it describes.

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?

Despite low complexity, the lack of annotations, output schema, and any parameter descriptions leaves important context unstated, such as how to obtain a valid sceneId, whether newName must be unique, and what the tool returns or does on failure. The description is too sparse to be considered complete for agent 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 description coverage is 0%, and the description does not mention sceneId or newName at all. With zero schema descriptions, the description was expected to compensate for parameter meaning, but it adds nothing beyond the parameter names themselves.

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 uses the specific verb 'Rename' and identifies the resource 'scene,' clearly distinguishing it from sibling tools that list, get, switch, create, remove, or clear scenes, and from rename_scene_collection. It is unambiguous and immediately communicates the tool's function.

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 provides no guidance on when to use this tool versus alternatives, no prerequisites (e.g., obtaining a sceneId via streamlabs_list_scenes), and no exclusions. An agent must rely solely on the tool name and schema to infer usage context.

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