manage_export_presets

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. It communicates a mutation operation but never discloses that the 'remove' action is destructive, whether adding a preset with an existing name overwrites it, or that changes likely persist to the project on disk. For a tool with a remove action and zero annotation coverage, this is a consequential gap.

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 six-word sentence with zero filler and the core purpose front-loaded. However, it is under-specified rather than genuinely concise: it covers only two of the three possible actions ('create or modify' versus list/add/remove) and includes no usage context that would help an agent decide.

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?

The tool has moderate complexity (5 params, 3 actions, no output schema) and zero annotations, so the description must carry more weight than it does. It fails to position the tool relative to export_project, disclose the destructive 'remove' behavior, or clarify overwrite semantics when adding a preset that already exists. An agent choosing between manage_export_presets, export_project, and manage_docker_export would be left guessing.

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 the schema already documents all five parameters with meaningful detail, including the action enum values, the required-for conditions on 'name', the 'platform' examples, and the default for 'runnable'. The tool description itself adds no parameter-level meaning, but the schema fully compensates, so the baseline 3 applies.

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 names a clear action ('Create or modify') and a specific resource ('export preset configuration'), so an agent can tell this tool is about export preset management in a Godot project. However, it omits the 'list' and 'remove' actions that the schema explicitly documents, understating the tool's actual scope. It also does not explicitly differentiate itself from the sibling export_project, which is the most closely related alternative.

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 nearby siblings such as export_project or manage_docker_export. There is no mention of the workflow relationship (e.g., configure presets before running an export), no exclusions, and no named alternatives. An agent must infer the usage context entirely from the schema's action parameter.

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