set_instance_overrides

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

With no annotations, the description carries full burden. While it mentions swapping and applying overrides, it fails to disclose critical behaviors: whether the operation is destructive, reversible, requires permissions, or what the response looks like. The ambiguity about 'previously copied' and the relationship between targetNodeIds and selection further reduces 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 concise at two sentences with no unnecessary words. However, it could be better structured by explicitly stating prerequisites and the role of the targetNodeIds, slightly reducing conciseness effectiveness.

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 no output schema, the description provides a functional overview but lacks key contextual details: how to copy overrides, whether selection overrides the parameter, and what happens if no overrides are available. Adequate but incomplete for a tool with moderate complexity.

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?

Input schema covers both parameters with descriptions (100% coverage), so the description adds little extra meaning. The description's mention of 'selected component instances' slightly contradicts the schema's requirement for targetNodeIds, suggesting ambiguity. Baseline score of 3 is appropriate as schema does the heavy lifting.

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 tool applies previously copied overrides to selected instances, swapping them to the source component. This distinguishes it from siblings like get_instance_overrides and set_text_content. However, the concept of 'previously copied overrides' is vague and not explained, slightly reducing clarity.

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 usage after copying overrides, but it does not explicitly state when to use this tool versus alternatives like get_instance_overrides or direct edit tools. No when-not-to-use guidance or prerequisites are mentioned, leaving the agent to infer context.

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