list_pipelines_sagemaker

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

There are no annotations, and the description merely states 'List SageMaker Pipelines'. It does not disclose any behavioral traits such as read-only nature, pagination, result ordering, or potential errors. With the full burden on the description, this is a significant gap.

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 concise sentence with no unnecessary words, achieving maximum efficiency and clarity.

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 extremely simple (no parameters, output schema exists), so a minimal description is arguably sufficient. However, it lacks any extra context about what the returned list contains or any limitations, making it only slightly above adequate.

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 tool has zero parameters and schema coverage is 100%, so there is nothing for the description to add about parameters. Baseline 4 applies.

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 'List SageMaker Pipelines' uses a specific verb and resource, clearly indicating that the tool lists SageMaker pipeline resources. It distinguishes from sibling list tools by naming the resource, even if it doesn't explicitly separate pipelines from pipeline executions; the tool name already does that.

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 provides no guidance on when to use this tool versus alternatives like list_pipeline_executions_sagemaker or describe_pipeline_sagemaker. It does not mention any prerequisites or typical scenarios, so the agent receives no direction on selection.

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