skypilot_api_status

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

readOnlyHint=true is consistent with a listing operation. The description adds a real behavioral trait beyond annotations: by default only pending and running requests are returned, and finished ones require all_status=True. That default-scope disclosure is valuable; return format and pagination behavior are left unstated but the output schema covers returns.

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 tight sentences, front-loaded with the core operation and followed by filter guidance. No wasted words; the filter list is slightly terse but not padded.

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 no explanation, and the description covers the operation plus most filter semantics. The only shortfalls are the undocumented 'fields' parameter and the absence of routing guidance against skypilot_get_request, both minor for a read-only list tool.

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%, so the description carries the load. It explains request_ids, cluster_name, all_status (with its semantic effect), and limit (caps results), but 'fields' is merely named with no indication of what fields are valid or what selecting them does. That is a meaningful gap for one of five params.

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 (List) and resource (API requests) with a clear default scope (pending and running). It does not, however, distinguish itself from the sibling skypilot_get_request, which an agent could reasonably confuse this with.

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 usage context for the filters (optional filtering, all_status to widen scope, limit to cap), which is implied guidance but not explicit when-to-use. It never states when to prefer this listing tool over skypilot_get_request for a single request, nor when-not to use it.

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