get_etl_pipeline_steps

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

With no annotations, the description carries the burden. It does disclose a useful behavioral trait ('deterministic') and implies a read-only metadata operation, but it omits error behavior, permissions, and any side-effect guarantees.

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?

A single, front-loaded sentence with no filler. The key scoping word ('one pipeline') appears at the end but the sentence remains efficient and informative.

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?

With an output schema available and a single parameter, the description is mostly adequate, but it lacks guidance on pipeline identification and error cases)Skip and does not clarify the relationship to sibling ETL pipeline tools. Adequate but not complete.

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 adds almost nothing beyond the schema's title. It confirms the operation targets 'one pipeline,' but does not explain pipeline_id semantics, source, or expected format.

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 uses a specific verb ('Return') plus a precise object ('deterministic ETL step metadata') and scope ('for one pipeline'). This clearly distinguishes it from sibling tools like get_etl_pipeline and get_etl_pipeline_dependencies.

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?

No guidance is given about when to use this tool versus alternatives, how to obtain a valid pipeline_id, or what conditions make this the right choice. The description states what it does but not when to call it.

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