edit_scene

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. 'Apply batch operations' is vague and does not reveal that the tool modifies the .tscn file on disk, whether operations are atomic, or how failures are handled. It implies mutation but provides no safety-relevant 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, front-loaded sentence with zero wasted words, which is commendable for conciseness. However, it leans toward under-specification for a complex, multi-operation tool, though that trade-off is handled by the schema. It earns a 4 for being succinct while not adding redundant 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 tool's complexity (nested operations array, no output schema, no annotations), the description is not complete enough for an AI agent to understand how to construct and apply batches safely. It lacks context on batch semantics, error behavior, and validation, despite the schema detailing individual parameters. A stronger description would explain the operational workflow and constraints.

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 coverage is 100%, with both parameters described in detail (path to .tscn file, list of operations including their own nested property descriptions). The description adds no additional parameter semantics beyond the schema, which is acceptable given the schema's thoroughness. Baseline of 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 it applies batch operations to a scene, using a specific verb and resource. It distinguishes this from sibling single-operation tools (e.g., add_node, remove_node, connect_signal) by the 'batch' qualifier, though it could be more explicit about the operation types (add/modify/remove nodes and connections) as seen in the schema.

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. It does not mention that it is intended for batched edits instead of calling individual scene-editing tools, nor does it state any prerequisites or exclusions. Given the large sibling list of granular tools, this is a notable gap.

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