set_z_offset

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

With annotations covering only the safety profile (not read-only, not idempotent, not destructive), the description adds genuinely useful behavior: immediate application including mid-print, and non-persistence across restarts. It omits the apparent confirmation flow (confirm/confirm_token) that a live machine mutation likely requires, which is the main remaining behavioral gap.

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 sentences, all front-loaded: purpose and sign first, mode semantics second, immediacy and persistence caveat last. No redundant or filler wording.

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?

An output schema exists, so return values need not be described, and the core action is well covered. For a live, non-idempotent mutation with a confirmation mechanism in the schema, however, the description should say when confirmation is triggered and what 'move' does — both are silently absent.

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 0% and the description only explains two of five parameters, but it adds high-value meaning for those: the unit and sign of 'offset' and the fact that 'mode' takes 'adjust' vs 'set' — values the schema does not enumerate. 'move', 'confirm', and 'confirm_token' are left entirely undocumented, so it only partially compensates for the coverage gap.

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 and resource ('Adjust the live Z offset (baby-stepping)') plus the sign convention ('positive raises the nozzle'), which is the single most important disambiguator for a numeric offset. The 'not persistent across restarts' clause implicitly separates it from save_z_offset without needing to name the sibling.

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?

Gives concrete when-to-use context ('mid-print, which is the usual way to fix first-layer squish') and explains the two operating modes. It stops short of explicit exclusions or naming save_z_offset for the persistence case, so it is clear context rather than full routing guidance.

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