set_instance_overrides

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly states the mutation: target instances are swapped to the source component and all copied override properties are applied. It does not mention reversibility or whether existing overrides are overwritten, but the core behavioral consequence is transparent.

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 two sentences, with the primary action in the first sentence and the result in the second. It is front-loaded, contains no filler, and every word contributes to understanding the tool's function.

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 two-parameter tool with no output schema, the description explains the operation well. It implies the prerequisite of copying overrides and using a selection. It could be more explicit about what 'overrides' are and the need for a selection, but this is adequately covered by the schema parameter descriptions, making the description complete enough for an agent to use correctly.

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?

The input schema provides 100% coverage with descriptions for both parameters (sourceInstanceId and targetNodeIds). The description text adds minimal extra semantic value beyond the schema, merely restating the roles of the source and target via context ('previously copied', 'selected'). This aligns with the baseline 3 for full schema coverage.

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 clearly states the action ('Apply previously copied overrides to selected component instances') and its effect ('Target instances will be swapped to the source component and all copied override properties will be applied'). It uses a specific verb and resource, and distinguishes from sibling tools like get_instance_overrides (retrieves overrides) and create_component_instance (creates new instances).

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 provides clear context for when to use the tool: it requires previously copied overrides and a current selection of component instances. It implicitly signals the workflow (copy first, then apply). However, it does not mention alternatives or explicitly state when not to use it, which prevents a 5.

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