skypilot_serve_download_logs

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

readOnlyHint=true is already declared, and the description usefully adds that the output lands in a caller-specified local directory (a local side effect not conveyed by the annotation). It does not disclose overwrite behavior, whether files are appended or replaced, or any auth/scope requirements for the target service, which matters for a 5-parameter tool.

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 short sentences, front-loaded with the core action and followed immediately by the optional filters. No filler, no repetition of the name or title.

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 described, and the annotation covers the safety profile. The gap is that half the parameters (tail, local_dir, service_name) are unexplained and there is no routing guidance relative to the similarly named log-viewing siblings, leaving the agent to infer key behavior.

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% and there are no enums in the schema, yet the description supplies the allowed target values ('controller', 'load_balancer', 'replica') and the purpose of replica_ids, which is genuine added meaning. It still leaves tail, local_dir, and service_name semantics entirely undocumented in both places.

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 and resource ('Download service logs to a local directory'), which clearly distinguishes it as a retrieval-to-disk operation rather than a viewing operation. However, it never names the close sibling skypilot_serve_logs, so an agent must infer the download-vs-display distinction on its own.

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 explains optional filtering by targets and replica_ids, which hints at when the filters are useful, but it gives no explicit when-to-use guidance and never contrasts itself with skypilot_serve_logs or skypilot_serve_status. Usage is implied by the 'download to a local directory' framing rather than stated.

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