skypilot_enabled_clouds

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

Annotations already establish readOnlyHint=true, so the safety profile is covered. The description adds real behavioral context beyond that: it states the return is a list of cloud names, and that expand=True changes the granularity by expanding Kubernetes and SSH into individual resource pools. It doesn't cover edge cases such as what happens when no clouds are enabled.

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 tightly packed sentences with the core purpose front-loaded, followed by the return value and then the two parameter behaviors. No filler or repetition; every sentence adds information.

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 small read-only listing tool with an output schema present, the description covers purpose, return type, both parameters, and the expansion behavior. There is no meaningful gap an agent would need to fill before invoking 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 description coverage is 0%, so the description must carry the param burden, and it does explain both parameters: expand=True expands Kubernetes/SSH into resource pools, and workspace scopes the listing to a workspace. It compensates well for the schema gap, though it could be more precise about the expanded output shape.

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 and resource with a qualifier that narrows scope meaningfully: 'List all clouds that have been enabled (credentials configured)'. This distinguishes it from sibling tools like skypilot_workspaces or skypilot_kubernetes_node_info, though it never names an alternative explicitly.

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?

Usage is implied rather than stated: you call it to discover which clouds are usable, and set expand=True when you want Kubernetes/SSH broken out into resource pools. There is no explicit when-to-use vs. when-not guidance and no named alternative, leaving the agent to infer the context.

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