interchange_get_pipelines

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral detail beyond annotations: it loads the asset, retrieves import data via UInterchangeManager, calls ID->GetPipelines(), and describes the returned fields. It does not cover error behavior when the asset is missing, but this is a minor gap for a read tool.

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 front-loaded with purpose and then explains process and return fields. It is appropriately sized, though the sentence 'Returns the class, name, and full object path of each pipeline' is partially redundant with the later 'Returns:' object shape. The redundancy is mild and does not obscure the core information.

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 a single-parameter read tool with annotations covering its safety profile, the description is nearly complete. It includes the return object shape even though no output schema exists, which is helpful. It leaves out explicit error handling and sibling routing, so it is not fully exhaustive.

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?

There is only one parameter and schema description coverage is 100%, so the schema already documents the asset_path format. The description implies the path identifies an asset whose import data is loaded, but adds no syntax or format details beyond what the schema provides. Baseline 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 states a specific verb and resource: list UInterchangePipelineBase instances stored on an asset's UInterchangeAssetImportData. It clearly distinguishes this operation from generic asset reads by naming the exact import-data object and pipeline type. An agent can understand what the tool returns without opening the schema.

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 gives no explicit when-to-use guidance or alternatives. It does not mention sibling tools such as interchange_get_asset_import_data or interchange_get_pipeline_properties, so the agent must infer when this list operation is preferable. Only the context phrase 'stored on an asset's UInterchangeAssetImportData' hints at usage.

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