Slice and wait for result

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

The annotations only say readOnlyHint=false and destructiveHint=false, so the description carries the burden of behavior. It discloses that the call blocks, returns stats and warnings, and avoids re-slicing if the plate is already sliced and unchanged. This adds meaningful behavioral context, though it doesn't elaborate on timeout behavior or what happens to concurrent slices.

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 short paragraphs with no filler. The core behavior is front-loaded, and the second paragraph adds valuable sibling routing without redundancy. Every sentence 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 tool with one optional parameter and no output schema, the description covers the blocking behavior, return value, cache semantics, and alternatives. Together with the schema's timeout documentation, an agent has enough to invoke it correctly.

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% and the only parameter, timeout, already has a full description in the schema including default and guidance. The tool description adds no further parameter-specific detail, so the baseline of 3 is appropriate.

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 ('Slice the current plate'), the blocking behavior, and the output ('final stats and warnings in one call'). It also differentiates itself from siblings by mentioning the non-blocking alternative and the cached-result behavior for unchanged plates.

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?

Explicitly says when this is the usual approach ('when you want the outcome immediately'), and names alternatives: 'use slice then poll get_slice_status' for non-blocking, and 'compare_settings' for sweeping settings. This is clear routing guidance.

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