Better Godot MCP

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

Annotations indicate destructiveHint=true, readOnlyHint=false, openWorldHint=false, and idempotentHint=false. The description doesn't contradict these annotations. While it doesn't explicitly restate the destructive nature, it lists actions like 'remove' and 'set_property' which imply mutation. The description adds value by enumerating the specific action types available, providing context beyond the annotations.

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 brief and front-loaded with the core purpose and action list. The two sentences are efficient with minimal waste. However, the second sentence 'Use help tool for full docs' could be seen as slightly redundant if the description itself were more complete, but it serves as a practical pointer.

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 complexity (9 parameters, destructive operations, no output schema), the description is insufficient. It doesn't explain what 'scene nodes' are, how actions map to parameters, what the tool returns, or error conditions. While annotations cover safety aspects, the description fails to provide adequate context for a tool with multiple mutation operations in a specialized domain (Godot).

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%, so the schema already documents all 9 parameters thoroughly. The description lists the action enum values but doesn't add meaningful semantic context beyond what's in the schema. It doesn't explain parameter dependencies or usage patterns. With high schema coverage, the baseline is 3, and the description doesn't significantly enhance parameter understanding.

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 'Scene node ops' which indicates operations on scene nodes in Godot, but it's vague about the specific domain (Godot game engine). It lists actions but doesn't clearly explain what a 'scene node' is or what resource it operates on. While it distinguishes from siblings by mentioning 'help tool for full docs', the core purpose remains somewhat ambiguous without context.

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 like 'scenes' or 'ui' from the sibling list. It mentions 'Use help tool for full docs' which implies additional documentation exists elsewhere, but gives no immediate context for tool selection. There are no explicit when/when-not statements or named alternatives.

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