octane_save_scene_manifest

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

With no annotations, the description carries the full burden. It discloses that the tool validates and saves a manifest and does not queue commands, but it lacks details on side effects, failure behavior, or return values. The primary behavior is clear but not comprehensive.

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 sentence, concise and front-loaded. However, it could include more detail without becoming overly long. It earns points for brevity but loses some for omitting parameter information.

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 vague input schema, lack of parameter descriptions, and no annotations, the description is insufficient for an agent to reliably construct a correct 'scene_plan'. The output schema exists but is not described, and the tool's validation behavior is not elaborated. The description is too sparse for a tool with such open-ended input.

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 elaborate on the 'scene_plan' parameter beyond calling it a 'semantic scene plan manifest'. The schema is vague (object with additionalProperties), and the description adds minimal guidance on expected structure 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 ('Validate and save') and the resource ('semantic scene plan manifest'). It differentiates from siblings that might queue commands by adding 'without queueing commands', though it could be more explicit about when to use this vs other save/load tools.

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 explicit guidance on when to use this tool versus alternatives like octane_load_scene_manifest or octane_validate_command. The description implies a use case (validating and saving without queuing) but does not provide when-not or trade-offs with sibling tools.

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