skypilot_managed_job_logs

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

The readOnlyHint annotation already covers the safety profile, and the description adds substantial behavioral context: snapshot semantics, default 100 lines with 0 meaning all, no streaming/following, and the controller/task switches. This goes well beyond what the annotation conveys.

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?

Front-loaded with the core purpose, then a series of compact, value-bearing sentences. No filler; each clause documents a distinct behavior or parameter.

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 needn't be described, and the description covers most parameters and the non-streaming behavior. The lone gap is the undocumented 'refresh' parameter, which is minor given the otherwise thorough coverage.

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?

With 0% schema description coverage, the description carries the burden and largely succeeds: it explains tail (default 100, 0 for all), name-or-job_id selection, task (name or 0-based index), and controller. Only the 'refresh' parameter is left unexplained.

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 ('Get a snapshot of logs from a managed job'), which an agent can distinguish from sibling tools like skypilot_job_logs and skypilot_managed_job_download_logs. It does not explicitly name those siblings, but the 'snapshot' framing and 'managed job' scoping are clear.

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?

'Does not stream/follow' signals this is a snapshot rather than a streaming operation, implying usage versus tools like skypilot_stream_and_get. However, it never names an alternative or states when to prefer this over download_logs or the regular job_logs, so routing is only implied.

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