manage_docker_export

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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it does almost nothing with that burden. It does not state where the Dockerfile is written, whether an existing Dockerfile is overwritten, what the 'read' action does, or what side effects (if any) occur on the project directory.

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 efficient sentence with the verb front-loaded and zero filler words. It loses a point because the brevity comes at the cost of omitting the tool's read mode, making it slightly under-specified rather than purely concise.

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 5-parameter tool with a mode-switching required parameter, no output schema, and no annotations, the description is incomplete. An agent would not know that 'action' supports reading an existing Dockerfile, what the tool returns, or how the parameters compose into a usable Dockerfile definition.

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 baseline is 3; the schema already documents all five parameters. The description adds only the 'headless export' framing, which hints at how godotVersion and exportPreset are used, but adds no detail about parameter formats or the create/read action semantics.

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 uses a specific verb+resource pair ('Create Dockerfile') with a clear context ('headless Godot export'), and this clearly separates it from siblings like export_project or manage_export_presets. However, it only covers the 'create' side of the tool while the required 'action' parameter explicitly supports both create and read, so the stated purpose is incomplete.

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 is given about when to use this tool versus the obvious alternatives (export_project, manage_export_presets, manage_ci_pipeline, run_project). There is no mention of CI/CD contexts, prerequisites, or when a Dockerfile is needed versus a direct export.

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