Download sliced gcode

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

The readOnlyHint: true annotation already indicates a safe read operation. The description adds useful context by specifying that it retrieves text and refers to the 'last successful slice', but it does not disclose behavior such as what happens if no slice has been performed or whether it triggers any side effects. This is additional but not extensive context.

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 a single, concise sentence that front-loads the action and outcome. Every word contributes to meaning, with no redundancy or unnecessary content.

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?

Given the tool's simplicity (no parameters, no output schema), the description is nearly complete: it explains what is retrieved and in what form. However, it does not specify the behavior when no successful slice exists, which could be a relevant edge case. The readOnlyHint annotation covers the safety profile, so this is a minor gap.

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 tool has zero parameters, so the baseline is 4. The description does not need to explain parameter meanings since there are none. It correctly focuses on the return value instead.

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 uses a specific verb 'Retrieve' with a clear resource ('G-code') and qualifier ('last successful slice', 'as text'). It clearly distinguishes from sibling tools like 'slice' (which generates) and 'get_slice_status' (which checks progress).

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 'last successful slice' implies this tool should be used after a successful slicing operation, but it does not explicitly state when to use it instead of alternatives or mention exclusions. The usage context is implied rather than articulated.

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