set_instance_overrides

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

The description discloses that instances will be swapped and overrides applied, but does not mention potential side effects (e.g., destructive nature, reversibility, required permissions). With no annotations, the description carries full burden and provides moderate transparency.

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 no fluff, front-loading the core action. Every word 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?

No output schema is provided, yet the description does not mention what the tool returns (e.g., success confirmation, updated IDs). The concept of 'previously copied overrides' is vague without reference to a preceding tool or process. Significant gaps for a mutation tool.

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 the schema already documents both parameters. The description adds little beyond the schema: it mentions 'source component' and 'target instances' but no additional semantic detail like format or constraints.

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 verb 'apply' and the resource 'previously copied overrides to selected component instances', and explains that target instances will be swapped to the source component with overrides applied. This distinguishes it from sibling tools like get_instance_overrides.

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 explicit guidance on when to use this tool versus alternatives. It mentions 'previously copied overrides' but doesn't explain how to copy them or what prerequisites are needed. There are no when-not-to-use scenarios or alternative tool references.

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