build_terrain

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

Discloses key behaviors: uses Gaea.Swarm.exe CLI, renders all output nodes, automatic -v placement, typical build time. With no annotations, this covers many behavioral aspects, though missing details on output or modifications.

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?

Three sentences with front-loaded purpose, no redundancy. Efficiently delivers key information without fluff.

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?

Description covers main purpose and notes automatic -v placement, but omits details on return value, prerequisites, and error handling. For a tool with 8 parameters and no output schema, it is moderately complete but has gaps.

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?

All parameters are described in schema (100% coverage). Description adds minor extra context about -v placement but does not significantly extend parameter meaning beyond 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?

Description clearly states it builds a terrain using a specific CLI and renders all output nodes. Verb and resource are well-defined, and it distinguishes itself from siblings like 'create_terrain' by focusing on the build process.

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?

Provides when to use the tool (build terrain) but does not explicitly compare with siblings or state when not to use. Lacks guidance on prerequisites or context for alternatives.

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