Set Instance Overrides

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

Annotations already declare idempotentHint and openWorldHint, so the description adds value by disclosing the swapping and application behavior. However, it does not clarify whether existing overrides on targets are replaced or merged, or what happens if the source component lacks overrides.

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?

Single sentence of 17 words, front-loading the action and key behavior. No wasted words; every part earns its place.

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?

Given the output schema exists (context signal), the description need not explain return values. It covers the core action and swapping behavior, but lacks context about prerequisites (e.g., needing to call instance_get_overrides first) or error conditions. Adequate for a tool with a clear purpose.

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 adds minimal context beyond the schema: it explains that overrides come from a 'previously-read' operation and that targets are swapped to the source component. This adds some meaning but is not essential.

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?

Description clearly states the action ('apply previously-read overrides') and resource ('target instances') with a specific behavioral detail ('targets are swapped to the source component'). Distinguishes from sibling 'instance_get_overrides' which reads, though could be more explicit about when to use this versus other instance mutating tools like 'instance_set_property'.

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?

Implies a prerequisite ('previously-read overrides') but does not explicitly state when to use this tool versus alternatives, nor when not to use it. The sibling list includes related tools, but no guidance is provided on choosing between them.

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