godot-mcp-pilot

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It mentions 're-writes it to disk' implying mutation and file system changes, but doesn't disclose permissions needed, whether it overwrites existing files, error handling, or what happens when 'newPath' is omitted. This leaves critical behavioral traits undocumented.

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 extremely concise—a single sentence that efficiently conveys the core functionality and optional behavior. Every word earns its place with no redundancy or unnecessary elaboration.

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 mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'save' entails operationally, what gets returned, error scenarios, or how it differs from other scene manipulation tools. Given the complexity of file system operations, more context is needed.

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 100%, providing good parameter documentation. The description adds marginal value by clarifying that 'newPath' creates a copy and that the operation involves disk writing, but doesn't explain parameter interactions or constraints beyond what the schema already states.

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 ('save a scene') and resource ('scene'), specifying it rewrites to disk and optionally to a new path. It distinguishes from siblings like 'create_scene' or 'read_scene' by focusing on saving existing scenes, but doesn't explicitly contrast with all similar tools like 'update_project_uids'.

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 mentions optional new path functionality but doesn't specify prerequisites, error conditions, or when to choose this over other scene-related tools like 'duplicate_node' or 'instantiate_scene'.

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