export_project

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

No annotations are provided, so the description carries full responsibility for disclosing behavior. It only mentions the export action and gives no information about side effects (e.g., file writes, overwrites), required permissions, duration, or whether the project needs to be loaded. This is a significant transparency gap for a likely mutating operation.

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 concise sentence, which is good for front-loading, but it is under-specified. It earns its place by stating the core purpose, but there is no additional detail to aid usage. It is not as minimal as a tautology, but it is not sufficiently informative for a tool with two required parameters.

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 that there is no output schema, no annotations, and only minimal parameter info, the description is far from complete. For a tool that likely performs a build/export operation, the description does not mention expected outcome, error conditions, or any relationship to other project lifecycle tools. It is inadequate for an agent to use it confidently without external knowledge.

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?

The schema description coverage is 0%, and the description does not explain the meaning or format of 'preset' or 'output_path'. While the parameter names are somewhat self-explanatory, the description adds no value beyond the names, leaving the agent to guess what presets are available and how the output path is used.

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 'Export the project via preset' clearly identifies the action (export) and the target (project), with the method (via preset) also indicated. It is specific enough to distinguish the tool from siblings focused on running, editing, or managing scenes and nodes, although it does not explicitly differentiate itself by naming alternatives.

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 any alternative, no prerequisites (e.g., project must be open, saved) and no exclusions. It simply states the action without context, leaving the agent to infer when export_project is appropriate.

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