omni_shape_hip_roof

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

With no annotations, the description carries the burden and does disclose the construction algorithm: layer-by-layer inset of 1 and apex fill. However, it does not state that this is a world-editing operation or whether existing blocks are overwritten, which is important for a shape tool with no readOnlyHint.

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 terse sentences with no filler; the main purpose is front-loaded and the algorithm is kept brief. The parenthetical '1 fill at apex' is cryptic, but the overall description is economical.

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 5-parameter shape operation with no annotations and no output schema, this description is incomplete. An agent cannot determine how to map from/to onto the footprint, how overhang affects the result, or what side effects the operation has.

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 0% and the description does not compensate: it never explains that from/to are the footprint coordinates, that overhang controls the inset, or what meta and block accept. The phrase 'Inset by 1 each layer' describes the default behavior but fails to mention the overhang parameter that can change it.

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 identifies a hip roof over a footprint, distinguishing it from sibling shape tools like omni_shape_gable_roof by shape type, and the algorithm sentences make the intended output concrete. It lacks an imperative verb such as 'creates/builds', relying on the tool name to supply the action.

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?

No guidance is given for when to choose this tool over alternatives such as omni_shape_gable_roof or omni_shape_pyramid. The only usage signal is the implicit 'use when you want a hip roof', with no exclusions or fallback conditions.

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