set_scene_name

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action of setting a name, but does not disclose potential side effects, reversibility, or any requirements such as the scene existing. This minimal disclosure is insufficient 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?

The description is a single concise sentence with no wasted words, which is appropriate for its simplicity. However, it may be too terse, lacking useful details, so it doesn't reach a perfect score.

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?

Given the tool's mutating nature, the lack of annotations, and the absence of any output schema explanation, the description is not complete enough. It fails to clarify scene indexing, error conditions, or what the return value might be, leaving significant gaps.

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, but it does not mention either parameter. While 'scene_index' and 'name' are somewhat self-explanatory, the description adds no additional meaning about how to use them, such as indexing base or constraints.

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 'Set a scene's name' with a specific verb and resource. It distinguishes itself from sibling tools like set_track_name and set_clip_name by specifying 'scene'. However, it lacks additional scope details that would make it a 5.

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, prerequisites, or how it compares to alternatives. There is no mention of when to rename a scene or what conditions must be met, leaving the agent without context for selection.

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