Export bundle

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

The description discloses that the tool produces a runnable bundle or .pck/.zip data pack, and lists presets if omitted. It clarifies the outcome of the operation. Annotations provide openWorldHint: true, which is consistent with the export action; no contradiction.

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 three sentences, front-loaded with the main purpose, and every sentence provides valuable information. No redundant or unnecessary text.

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?

With 6 optional parameters and no output schema, the description covers the main outcomes and mode distinction well. It explains the preset listing behavior. It does not detail the return format beyond what the schema says, but the tool's purpose is clear enough for an AI agent to use.

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 coverage is 100% with each parameter having a description. The tool description adds context for the 'mode' enum (linking to bundle vs pack), but the schema already explains all parameters adequately. Baseline is 3 due to high schema coverage.

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 'Export a project using a preset from export_presets.cfg' and explains the three modes (release/debug for runnable bundle, pack for data pack). It also specifies that omitting preset lists available presets, distinguishing it from sibling tools like export_mesh_library or export_project.

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 mode-specific usage guidance (when to use release/debug vs pack) and explains the behavior when no preset is given (lists presets). However, it does not explicitly compare against sibling export tools, missing some guidance on tool selection.

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