list_job_steps

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only repeats the basic operation ('List all steps/tasks') without explaining what a step/task is, whether the result is flat or nested, what happens for jobs with no steps, or whether any permissions are required. This is a noticeable gap for a tool with no structured safety annotations.

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?

The description is a single, focused sentence with no filler, and the operative word 'List' is front-loaded. Every word contributes to understanding the tool's core purpose.

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?

For a simple one-parameter list tool, the description captures the essential operation but lacks guidance on selecting it among sibling job-related tools and provides no information about the return shape or behavioral semantics. Since there is no output schema and no annotations, a bit more context would make the definition more self-sufficient.

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?

The schema already provides 100% coverage of the single parameter, including its UUID format and the description 'The job UUID'. The tool description adds only the general sense that job_id refers to the job whose steps are listed, which does not materially extend the schema's meaning.

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 ('List') and a clear resource ('all steps/tasks for a job'), which clearly distinguishes it from sibling tools like list_jobs, list_child_jobs, and get_job. Even without reading the schema, an agent knows this tool retrieves the component steps/tasks of a single job.

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 implies the tool is used when you need steps/tasks for a specific job, and the required job_id parameter reinforces this. However, it does not explicitly mention when to prefer this over alternatives such as list_jobs, list_child_jobs, or get_job, nor does it state any exclusions.

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