skypilot_managed_job_download_logs

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

readOnlyHint=true already covers the safety profile, so the description is not required to restate it. It does add useful behavior: the controller=True switch redirects output to controller logs, and local_dir controls the save location. However, the refresh parameter's effect is never explained, leaving a behavioral gap.

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?

Four short sentences, front-loaded with the core action and then the selection/option details. No filler, though it is slightly list-like rather than tightly structured.

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. For a 5-param read tool this is mostly adequate, but the unexplained refresh parameter and the lack of any name/job_id mutual-exclusion note leave an agent with missing decision context.

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 carries the param burden. It meaningfully explains name, job_id, controller, and local_dir (4 of 5), but refresh is undocumented in both the schema and the description, and no guidance is given for resolving name vs. job_id conflicts.

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 (Download) and resource (logs from a managed job) with a clear destination (local directory). It is distinguishable from skypilot_managed_job_logs (view vs. download) only by inference, not by explicit contrast, so it falls short of a 5.

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?

It says how to select a job (name or job_id) and when to use the controller flag, but gives no explicit guidance on when to prefer this tool over skypilot_managed_job_logs or skypilot_download_logs. Usage is implied rather than stated.

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