interchange_set_pipeline_properties

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

Annotations already declare readOnly=false, destructive=true, idempotent=true, so safety is covered, but the description adds real value: it explains the reflection mechanism and that unknown/non-editable fields are skipped and reported, plus the return field structure (applied_count, skipped, note). It does not state whether changes persist without an explicit save.

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 compact sentences with the action and value shape front-loaded, then return fields. No filler, though the return-value listing could be tightened since the fields are self-descriptive.

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 no output schema present, the description usefully documents the return shape, and it covers the input value types. Given annotations carry the safety profile and the schema carries parameter detail, the remaining gap (persistence/save semantics after a mutation) is minor.

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-schema. The description restates the {name: value} shape and the scalar/struct/array value types, which is largely duplicative of the schema's own wording, so 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 ('Set properties') and resource ('Interchange pipeline asset') plus the mechanism ('by reflection'), so the agent knows exactly what action is performed. It does not explicitly distinguish itself from near siblings like interchange_get_pipeline_properties or interchange_set_pipelines, but the verb+resource 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?

No guidance on when to use this versus alternatives such as interchange_set_pipelines, interchange_set_pipeline_stack_default, or interchange_save_pipeline. Usage is only implied by the name; the agent gets no conditions, prerequisites, or exclusions.

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