ai_pipeline_steps_list

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

No annotations provided, so description carries burden. 'List' implies read-only but not explicitly stated. No disclosure of side effects or safety characteristics. Adequate but could be clearer.

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?

Two sentences, front-loaded with purpose, no redundant information. Efficient and clear.

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 list tool with 3 parameters and no output schema, description covers core purpose and return fields. Missing details on connection and include_inactive parameters, but overall 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?

Schema coverage is 33%; only pipeline has schema description. Description reinforces pipeline parameter but does not clarify connection or include_inactive parameters. It does mention return fields, adding some value.

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?

Description clearly states it lists ai.pipeline.step records for a given pipeline name and mentions specific fields shown (sequence, model.method, etc.), distinguishing it from sibling tools like ai_pipeline_run or ai_pipeline_step_execute.

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?

Implicit usage context but no explicit when-to-use or when-not-to-use. No mention of alternatives like ai_pipeline_step_execute for running steps. Could be improved with a note about not modifying data.

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