scene_manage

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

No annotations are present, and the description lacks any information about behavioral traits such as side effects, destructive actions, authorization requirements, or return behavior. This is a critical gap for a tool managing scene operations.

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 too short (two sentences) to be useful. The first sentence is too generic, and the second redirects to another tool. It sacrifices completeness for brevity, making it ineffective.

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 (14 enum operations, nested params) and the absence of annotations and output schema, the description is severely incomplete. It fails to explain any operation details, parameter usage, or expected results.

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%, so the baseline is 3. The description does not add meaning beyond the schema's parameter descriptions ('Operation in the scene branch' and 'Parameters for the selected operation').

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 'Godot scene operations' is vague and does not specify what the tool does. It does not differentiate from sibling tools like node_manage or animation_manage.

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 instructs to 'call godot_catalog for the operation tree' but provides no guidance on when to use this tool vs alternatives such as node_manage or animation_manage.

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