list_pipeline_pods

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

With no annotations, the description carries the full behavioral burden. It adds one meaningful trait: an empty result when pods are gone, which prevents the agent from misreading an empty list as an error. It does not disclose read-only semantics, ordering, or failure modes, but the edge-case note is a valuable disclosure.

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 two short sentences with the core action front-loaded and the behavioral nuance second. Every word contributes information, and there is no filler or redundancy.

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 three required parameters and zero schema descriptions, the tool is underspecified for correct invocation: parameter meanings and constraints are missing. The output schema covers return values, so that part is fine, but the input side is not adequately documented.

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 the description does not explain what request_id, step_index, and replica mean. The 'one job' phrase hints that request_id identifies the job, but the agent is left guessing about step_index and replica semantics. This is insufficient for a 3-required-parameter tool.

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 gives a clear verb-resource pair: list pods for one specific job. The 'Empty if they are already gone' line adds useful scoping, and the sibling get_pipeline_pod implies the single-vs-list distinction, though it is not stated explicitly.

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 establishes the context for use: listing pods for a single job. However, it never mentions alternatives like get_pipeline_pod or list_pipeline_jobs, nor does it state when this tool should not be used, so routing among siblings is left to inference.

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