Get slice status

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

The readOnlyHint annotation already marks this as a safe read, and the description adds useful behavioral context: it is a polling endpoint, 'idle' represents no/cancelled slice, and warning/error details are included. No contradiction with annotations.

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 compact, front-loaded with the most important state semantics, and every sentence earns its place. It explains behavior, caveats, and alternatives without repetition.

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 no-parameter, read-only status tool without an output schema, the description is complete: it covers states, stats, warnings, polling guidance, and idle meaning. The sibling references prevent misuse.

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 there is no schema gap to compensate for. The description goes beyond the schema by explaining what the returned state field contains, which is the closest relevant semantic info.

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 the exact resource (slice status), the kind of information returned (state, stats, warnings/errors), and the possible state values. It also distinguishes itself from sibling tools by naming what get_slice_warnings and get_slice_breakdown cover.

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 to poll after slicing to track progress and read results, defines what 'idle' means, and points to siblings for narrower or different data. This gives an agent clear selection criteria.

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