list_pipeline_execution_steps_sagemaker

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 states that the tool lists all steps, but does not mention pagination behavior, whether the execution must be in a particular state, authentication needs, or any read-only caveats. The verb 'list' implies read-only, but this is not explicit.

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, front-loaded sentence that names the verb and resource with no redundant words. It is appropriately sized for a simple, one-parameter list operation.

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?

The tool is simple, has one fully documented parameter, and provides an output schema. However, the description does not mention prerequisites (beyond the required ARN), pagination, or relationship to sibling tools. It is adequate for a straightforward list operation but lacks some context that would make it fully 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?

The schema already describes the single parameter (pipeline_execution_arn) with 100% coverage, including its purpose. The tool description adds no extra semantic detail beyond what the schema provides, so the baseline of 3 is appropriate.

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 ('List') and a precise resource ('Pipeline Execution Steps' for a SageMaker Pipeline Execution). It clearly differentiates this tool from siblings such as list_pipeline_executions (which lists executions) and describe_pipeline_execution (which describes a single execution).

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 does not explicitly state when to use this tool or provide alternatives. However, the purpose and the required pipeline_execution_arn parameter imply that it should be used when you have an execution ARN and want to see its steps. This is implied usage rather than explicit guidance.

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