Godot Batch Workflow Manager

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

Annotations already provide destructiveHint: true. The description adds behavioral details: bounded execution (implied by maxSteps), dryRun capability, and stopOnError. No contradiction; it supplements the annotations with additional constraints.

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 two sentences, front-loading the core purpose without any extraneous information. Every sentence serves a clear role.

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?

While the description covers purpose and usage context, it omits details about execution order (sequential), result aggregation, and that steps can call any Godot tool. Output schema exists but is not shown; given the tool's complexity, more execution behavior context would improve completeness.

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%, and each parameter is already described in the schema (steps, dryRun, maxSteps, stopOnError). The description adds no additional meaning beyond what the schema provides, so baseline score 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 explicitly states the tool runs a bounded sequence of other Godot MCP tool calls, using specific verb 'run' and resource 'bounded sequence'. This clearly distinguishes it from sibling tools that handle individual asset, doc, editor, etc. tasks.

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 indicates it is 'useful for Codex multi-step workflows and recovery loops', providing clear context for when to use. However, it does not explicitly state when not to use or compare to alternatives (e.g., using individual tools directly).

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