manage_terrain

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It does not mention that some actions are destructive (e.g., clear_region, write_voxels) or that others are read-only (e.g., read_voxel, colors_get). It also does not disclose any permissions, side effects, or constraints. The description only lists operations without behavioral context.

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 sentence with a clear, list-like structure, front-loading the purpose. It is concise and covers the major capabilities. However, it could be more structured (e.g., separating read and write operations) to improve scannability.

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 the high complexity (26 parameters, multiple actions) and no output schema, the description provides a high-level overview but lacks details like which parameters are required for which actions. However, the input schema is very detailed with per-parameter descriptions and usage per action, which compensates. The description alone is not fully complete, but combined with the schema it is adequate.

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 100%, so the baseline is 3. The description does not add additional meaning beyond what is already in each parameter's description. It merely categorizes operations but does not provide examples or contextual details that enhance understanding.

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 that this tool handles terrain operations, listing specific categories like fill shapes, clear regions, replace materials, manage colors, read/write voxels, generate procedural terrain, and smooth terrain. It distinguishes itself from sibling tools which cover other domains (animation, assets, audio, etc.). However, the description does not single out a specific verb-resource pair, instead listing many capabilities, which slightly reduces clarity.

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 does not provide any guidance on when to use this tool versus alternatives or when not to use it. It only lists what the tool does, without explicit context or exclusions. While sibling tools are clearly different domains, the absence of usage instructions is a gap.

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