interchange_set_pipelines

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

Goes well beyond the annotations by disclosing that SetPipelines resets TransientPipelines (what is destroyed), that the package is marked dirty so the change persists only on save, and that unresolvable paths are reported but do not abort the call. This is exactly the extra context annotations cannot convey.

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?

Front-loads the primary action and then layers behavior and return shape efficiently. Some implementation details (header/.cpp citations) are noise for tool selection, but the description remains reasonably tight and well-ordered.

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?

Even without an output schema the description enumerates the return fields, and the annotations cover the mutating/idempotent/destructive profile. It is nearly complete; the only gap is the absence of guidance for disambiguating from sibling pipeline tools.

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 100%, so both parameters are already documented in the schema, including the LoadObject resolution and unresolved_paths behavior. The description largely restates this, adding only marginal value, so the baseline 3 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?

States a specific verb (Replace/Set) and resource (the UInterchangePipelineBase stack on an asset's UInterchangeAssetImportData), plus the exact API called. It does not name distinguishing siblings such as interchange_set_pipeline_stack_default or interchange_set_pipeline_properties, so the agent must infer the boundary, but the core purpose is unambiguous.

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 explains mechanics but never says when to choose this tool over the closely related interchange_set_pipeline_stack_default, interchange_set_pipeline_properties, or interchange_get_pipelines. There are no explicit when-to-use or when-not conditions, leaving selection to inference.

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