set_instance_overrides

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

Describes the core behavior (swap and apply) but lacks detail on side effects, such as whether the source component is modified or what happens if no overrides have been copied. No annotations provided, so description carries the burden, and it's adequate but not rich.

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 sentences, front-loaded with the action, no wasted words. Efficiently conveys the purpose and behavior.

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?

Covers purpose and behavior for a tool with 2 required params and no output schema. Missing explicit mention of the prerequisite that overrides must have been copied beforehand. Mostly complete with one notable gap.

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% and the description adds a minor detail ('expected names for verification'). Baseline 3 is appropriate as the description adds limited value beyond the schema.

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?

Clearly states the verb 'Apply' and the resource 'overrides to selected component instances', explaining the effect of swapping and applying properties. Distinguishes from siblings like 'get_instance_overrides' and 'set_component_instance_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?

Implied that overrides must have been previously copied, but no explicit when-to-use or when-not-to-use guidance. No alternative tools are referenced, leaving the agent to infer prerequisites.

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