Godot Scene Manager

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

The annotation declares destructiveHint: true, so the description's mention of creation/node operations aligns. The description adds 'headless' context, which is useful beyond annotations. However, it does not elaborate on side effects, permissions, or error conditions.

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 with no wasted words, but it is vague and lacks structure. It does not front-load critical information or use bullet points. Could be more informative without added length.

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?

With 11 parameters, a single sentence is insufficient to cover the tool's scope. While an output schema exists, the description fails to convey key details like which actions are read-only vs destructive, or how steps work. The tool is complex but the description is too brief.

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 high (91%), so the description does not need to explain parameters in detail. The description provides minimal extra meaning beyond the schema, simply restating the action types. 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 reads scene text and performs headless scene creation/node operations. It uses a specific verb-resource combination ('Read...perform'). However, it does not distinguish from sibling tools like godot_asset or godot_batch, which could also involve scene operations.

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 vs alternatives. The description does not mention prerequisites, when-not to use, or suggest alternative tools for specific scenarios.

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