design_set_building_style

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

No annotations are provided, so the description carries the full burden. It indicates a mutation of an existing layer but says nothing about whether the change is reversible, what happens if the target layer is not a building, or whether existing geometry is destroyed — all critical for a style-mutation tool with no annotation safety profile.

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 first sentence is well-formed and front-loaded, but the second sentence is a verbatim restatement of the 24-value enum already present in the input schema, consuming roughly half the description with zero added information.

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 simple two-parameter tool with a complete schema and no output schema, the core action is covered. However, prerequisites (a building layer must exist), failure modes, and the relationship to design_list_architecture_styles / design_add_building are unaddressed.

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% and the style enum is already fully defined in the schema, so the enumerated list in the description adds no new semantics. The layerId fallback behavior (omit to use first building layer) lives in the schema, not the description, leaving this at the baseline.

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?

States a specific verb ('change') and resource ('architectural style of an existing building layer'), which is precise enough to distinguish it from creation-oriented siblings like design_add_building. It stops short of naming a concrete alternative such as design_list_architecture_styles, so differentiation relies on the reader's inference.

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 phrase 'existing building layer' implies a building must already exist, but the description never says when to use this versus design_add_building or how to discover/reset styles. There are no explicit exclusions, prerequisites, or alternative routes given.

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