create_stairs_3d

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

With no annotations, the description carries the full disclosure burden. It explicitly reveals a destructive side effect ('Replaces the previous ones of that level') and clarifies the generated geometry ('solid blocks from the floor up to each tread'). It does not discuss reversibility or the view parameter, but the core behavior is transparent.

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 two sentences with no filler. It front-loads the action and scope, then adds geometry context and the replacement side effect. Every sentence contributes useful 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?

The main action, scope, geometry, and side effect are all covered, and the presence of an output schema means return values do not need detailed explanation. However, the description leaves the `view` parameter undocumented and does not state prerequisites such as whether the active level must already have a floor, leaving some completeness 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?

The only parameter, `view`, is not mentioned anywhere in the description. Schema coverage is 0%, and the description does not clarify whether `view` controls a preview, toggles the 3D view, or determines something else. The default value of `true` is not enough to make this optional parameter meaningful.

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 states a specific verb and resource: 'Build the 3D steps of every stair of the active level.' It also defines scope, geometry ('solid blocks from the floor up to each tread'), and a distinguishing side effect ('Replaces the previous ones of that level'), which separates it from sibling tools like create_stair.

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 gives useful context ('active level') but provides no guidance on when to use this tool versus alternatives. It does not mention the sibling create_stair tool or any exclusion criteria, so an agent must infer the appropriate choice from the name alone.

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