create_terrain

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

Discloses that the file is saved in the project directory and is empty, upfront. No annotations provided, so description carries burden adequately.

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?

Two sentences plus workflow list, no fluff. Front-loads purpose and file type immediately.

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?

For a 1-parameter creation tool with no output schema, the description provides complete context: software version, file location, and next steps.

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?

Adds concrete example and constraint (no extension) beyond the schema's property description, which alone says 'Filename without extension'.

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 it creates a new empty .terrain file for Gaea 2.2.9, distinguishing it from siblings like build_terrain (which likely builds from existing data).

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 a typical workflow showing create_terrain as the first step, guiding when to use it. Lacks explicit when-not-to-use instructions but context is clear.

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