scene_order

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

With no annotations, the description carries the full burden but only says 'Sets the order of scenes.' It does not disclose whether scene names must already exist, whether the order replaces the current one, or what happens on invalid input. This is minimal and lacks behavioral context.

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, efficient sentence that directly conveys the purpose. It avoids fluff and is front-loaded. While it is sparse, it is not under-specified to the point of causing confusion.

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 setter tool with one parameter and an output schema present, the description is adequately sized. However, it lacks any explanation of behavioral effects or prerequisites, which would improve completeness. The schema and output schema fill some gaps, but the description leaves room for interpretation.

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?

The schema description for the single parameter 'scene_list' is fully covered (100%) and includes an example: 'Space-separated scene names in the order wanted, e.g. "F2 F1 F3".' The tool description itself adds nothing beyond the schema, but since coverage is high, the baseline 3 is appropriate.

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 tool's action: 'Sets the order of scenes.' This is a specific verb and resource, and it distinguishes from sibling tools like 'scene' by focusing on ordering. However, it does not elaborate on how the order is applied, but the parameter schema partially covers that.

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. There is no mention of prerequisites, exclusions, or alternative tools. It only states what the tool does, leaving the agent without context for selecting it.

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