interchange_create_pipeline_asset

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

Annotations already declare idempotentHint=true and destructiveHint=false, but the description adds useful specifics: exactly what idempotency means here (returns the existing object with already_existed:true) and documents the return shape. It does not cover permissions or failure modes.

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 action and resource, then adds idempotency behavior and return fields in two short sentences plus one inline return signature. No filler.

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 annotations covering safety/idempotency and no output schema, the description supplies the missing return shape and idempotent-return behavior. All three parameters are documented in the schema, and the default package_path is stated there.

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 coverage is 100%, so the baseline is 3. The description goes beyond the schema by enumerating the concrete pipeline families accepted by pipeline_class_path (generic texture, mesh, material, animation, audio, scenes, groom, assets, glTF, sparse volume texture, MaterialX), which helps an agent select a valid class.

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 and resource: create an Interchange pipeline asset of a concrete pipeline class. The parenthetical enumeration of supported pipeline families makes it easy to distinguish from generic asset-creation siblings.

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 what the tool creates but gives no when-to-use guidance, prerequisites, or alternatives relative to other Interchange tools such as interchange_import_asset or interchange_set_pipelines.

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