interchange_set_pipeline_stack_default

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

Annotations already flag destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so safety is covered. The description adds meaningful context beyond them: the change is saved persistently to the project's default config and it targets a specific settings object, plus it discloses the return shape.

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?

Two tight sentences plus a compact returns line; the core action and target are front-loaded with zero 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?

For a small mutation tool the description is largely complete: it identifies the exact setting changed, its persistence, and the return payload, and annotations cover the safety profile. It omits only prerequisite behavior (what happens if stack_name is not a valid key).

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 (stack_name, content_or_scene, including the case-insensitive hint and FName key semantics) are already fully documented in the schema. The description adds no parameter detail beyond what the schema provides.

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+resource ('Set the default Interchange pipeline stack') and names the exact target objects (DefaultPipelineStack of ContentImportSettings or SceneImportSettings), which cleanly distinguishes it from siblings like interchange_set_pipelines and interchange_set_pipeline_properties.

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 implies its scope ('for content or scene import') but never states when to prefer it over the sibling pipeline setters or what prerequisites exist (e.g., the named stack must already exist). Usage is only implied.

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