edit_scene_nodes_graph

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

With no annotations provided, the description must carry the full burden. It discloses 'per-operation rollback' but omits details like failure semantics, whether the batch is atomic, permission requirements, or response format. This is minimal.

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 not bloated. However, it is so brief that it lacks necessary context, and there is no structure or breakdown to aid comprehension. It's concise but under-specified.

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 tool with four parameters including a required array of complex operations, and with no annotations or output schema description, the description is severely incomplete. It doesn't explain the operations format, the purpose of layout/debug_path, or what the response contains. An agent would have little idea how to construct a valid call.

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 mentions no parameter details. The only hint is 'operations' in the phrase 'Scene Nodes graph operations', but it doesn't explain the operations array structure, layout, debug_path, or layout_after_batch. The description adds almost no meaning beyond the schema.

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 states a clear verb ('Apply') and resource ('Scene Nodes graph operations'), and mentions 'per-operation rollback' which distinguishes it from inspection/layout tools. However, it doesn't enumerate what operations are supported or differentiate from edit_capsule_graph explicitly.

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 guidance on when to use this tool versus alternatives. It doesn't mention that it's for scene nodes as opposed to capsule graphs, nor does it specify prerequisites or typical use cases.

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