lay_flat

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

With no annotations, the description carries the full burden, and it does disclose one genuine behavioral trait: 'attempt' signals this is best-effort and may not succeed. However, it says nothing about whether the STL is modified in place or a new file/geometry is returned, nor about failure behavior, which are the key traits for a mutation-style tool.

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?

One front-loaded sentence that states the action and the target geometry with no filler. Every word earns its place.

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 one-parameter geometry operation with no output schema and no annotations, the description explains the transformation adequately but leaves the agent unsure about persistence (in-place vs. return value) and failure modes, which matter for calling it correctly in a pipeline with slice_stl/print 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?

Schema coverage is 100% for the single stl_path parameter, so the schema already documents it fully. The description adds only the geometric goal, not any additional parameter meaning; baseline 3 applies.

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 gives a specific verb (rotate) plus the exact geometric outcome (largest flat face onto the XY plane at Z=0), which clearly separates it from the generic rotate_stl sibling even though it does not name that sibling. The only gap is the lack of an explicit contrast with rotate_stl/translate_stl/center_model.

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?

There is no guidance on when to prefer this over rotate_stl or center_model, no stated prerequisites (e.g., mesh must be watertight or have a detectable flat face), and no note about what happens if no flat face exists. The agent must infer usage entirely.

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