set_scene_name

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the mutation/safety profile is covered by structured data and the word "Rename" only restates it. The description adds nothing beyond that: no note on whether renaming is reversible, what happens if index is out of range, or whether the previous name can be recovered.

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 short sentence with the verb and resource front-loaded and no wasted wording. Its brevity is efficient, though it trends toward under-specification rather than economy for a tool with two undocumented parameters.

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?

An output schema exists, so return values need not be described, but for a two-argument mutation tool with zero parameter documentation the description should at minimum pin down the index semantics and any precondition. It leaves an agent guessing about scene addressing, which is the main risk when calling it.

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%, so the description must compensate, and it largely does not. The "Verse"/"Chorus" examples give some sense of what 'name' accepts, but 'index' — the more ambiguous parameter, likely the scene slot — is never explained, leaving open whether it is zero-based and how it relates to scene position.

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?

States a specific verb and resource ("Rename a scene") with example values that make clear this sets a scene's display name. It is distinguishable from nearby siblings such as set_clip_name, set_track_name, and set_arrangement_clip_name by naming the scene as the target, though it never references those alternatives.

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 when-to-use or when-not-to-use guidance is given, and no prerequisites are mentioned (e.g. that the scene must already exist, or that create_scene should be used first). The parenthetical name examples hint at typical values but are not usage guidance.

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