gaea_run_build

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

There are no annotations, so the description carries the full burden of disclosing side effects. It only says 'Run Gaea.Swarm.exe' without mentioning that it likely executes an external build process, writes outputs, requires a configured environment, or has a dryRun default of true. This leaves the agent unaware of important behavioral consequences.

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 concise, but it is under-specified for a tool with 10 parameters and no annotations. The single sentence earns its place for purpose but omits critical semantic and usage detail, making it too short to be properly structured.

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?

This is a complex build-execution tool with 10 parameters, a nested object, no output schema, and no annotations. The description gives only the basic action and resource, leaving out paramaters, side effects, prerequisites, return behavior, and relationship to sibling tools.

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 0%, and the description mentions none of the 10 parameters. There is no explanation of what 'graph', 'seed', 'vars', 'dryRun', 'region', 'profile', or 'resolution' mean, so the description offers no help beyond the raw schema.

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 ('Run') and resource ('Gaea.Swarm.exe') tied to a .terrain graph, making the tool's purpose immediately understandable. It clearly differentiates from siblings like gaea_list_graphs, gaea_open_graph, and gaea_set_variable, which are all non-execution operations.

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 alternatives, nor any prerequisites such as setting variables, configuring output, or opening a graph. Siblings like gaea_set_build_output and gaea_set_variable exist, but the description does not explain the expected workflow.

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