skypilot_pool_download_logs

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

readOnlyHint=true already declares this as a safe read, so the burden is lower. The description adds that logs are written to a local directory and that filtering is optional, but does not mention overwrite behavior, whether the local dir is created, or how much is downloaded by default (tail is unexplained).

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?

Two tight sentences, front-loaded with the action and destination. No filler, though the second sentence packs two filter parameters without explaining the tail parameter at all.

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 not be explained. But with 5 parameters at 0% schema coverage and no annotations beyond readOnly, the description leaves tail, pool_name, and local_dir semantics unstated, which is a gap for a download 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 must compensate; it supplies the allowed values for targets ('controller', 'load_balancer', 'replica') and mentions worker_ids filtering. However pool_name, local_dir, and especially tail (a numeric limit) remain undocumented in both description and 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?

Specific verb+resource: 'Download worker pool logs to a local directory' clearly states what the tool does and its destination. It implicitly separates itself from related siblings by scoping to 'worker pool' logs, though it does not explicitly name the sibling variants (pool_logs, serve_download_logs, etc.).

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?

No when-to-use guidance, no exclusions, and no alternatives named among the many log/download siblings (skypilot_pool_logs, skypilot_download_logs, skypilot_serve_download_logs). The mention of optional filtering is parameter guidance, not usage routing.

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