skypilot_job_logs

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

With readOnlyHint=true, the safety profile is already known, but the description adds important behavior: it returns a snapshot, not a stream; it shows the last N lines with default 100 and 0 meaning all; and it defaults to the latest job when job_id is omitted. These details go beyond the annotation and help the agent invoke it correctly.

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 short sentences, front-loaded with the core action, followed by behavioral clarifications. No wasted words; every sentence adds useful information about the returned data or parameter behavior.

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?

Given the tool's simplicity, the presence of an output schema, and the readOnlyHint annotation, the description is nearly complete. It covers snapshot behavior, tail semantics, and job_id fallback. The only minor gap is that it does not mention cluster_name explicitly or prerequisites like the cluster being running, but these are largely inferable.

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 parameter meaning. It explains tail's default and the special value 0 for all lines, and it explains job_id's fallback behavior when omitted. cluster_name is required but self-evident from context, so the description compensates well for the lack of schema descriptions.

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 states a specific verb and resource: 'Get a snapshot of logs from a job running on a cluster.' It is clear, though it does not explicitly distinguish this tool from similar siblings like skypilot_managed_job_logs or the various download_logs tools. The scope 'job running on a cluster' is helpful but not a full sibling differentiation.

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 provides behavioral context ('snapshot', 'Does not stream/follow logs') and a default for missing job_id, which implies when to use it, but it does not explicitly say when to choose this tool over alternatives such as skypilot_managed_job_logs or skypilot_download_logs. No exclusions or direct alternatives are named.

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