skypilot_serve_terminate_replica

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

The destructiveHint annotation already signals that this is a destructive operation. The description adds useful behavioral context beyond that: purge=True overrides errors during termination, and the call returns a request_id. It does not explain graceful shutdown or failure modes in detail, but it meaningfully enriches the annotation.

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 short sentences with zero waste. The purpose is front-loaded, the purge behavior follows logically, and the return value is stated last. 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?

An output schema exists, so the description need not detail return values, though it helpfully mentions request_id. The destructiveHint annotation covers the safety profile, and the description covers the core action and purge behavior. Missing details about prerequisites or post-termination service state are minor for this narrow operation.

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 description coverage is 0%, so the description must carry parameter meaning. It explains purge well ('force termination even with errors') but says nothing about service_name or replica_id beyond their self-evident names and the phrase 'replica of a service'. This is adequate but leaves some gaps for a low-coverage schema.

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 ('Terminate') and a precise resource ('a specific replica of a service'), making the core action unambiguous. However, it does not explicitly differentiate itself from sibling operations like skypilot_serve_down or skypilot_serve_update, so it stops short of the top score.

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 description says nothing about when to choose this tool over alternatives such as terminating the whole service with skypilot_serve_down. The only conditional guidance is for the purge parameter, which is parameter-level rather than tool-selection guidance.

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