get_instance_overrides

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

No annotations are provided, so the description must convey safety. The verb 'Get' implies a read-only operation, but the description doesn't explicitly state that no modifications occur. It adds useful context about the lifecycle of overrides, but falls short of disclosing error behavior, return format, or side-effect guarantees.

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 ('Get all override properties'), and no filler words. The second sentence provides valuable context about usage without redundancy.

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 simple getter with one optional parameter and no output schema, the description adequately conveys the tool's purpose and the meaning of 'overrides'. However, it doesn't detail the exact structure of the returned override properties, which would be helpful for agents, so it loses one point.

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% (the only parameter 'nodeId' is fully described). The description's phrase 'selected component instance' adds no new meaning beyond the schema. Since the schema already documents the parameter well, baseline 3 is appropriate.

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 uses a specific verb ('Get') and resource ('override properties from a selected component instance'), clearly distinguishing it from the sibling tool 'set_instance_overrides'. It also explains the broader purpose of applying overrides to other instances, adding context beyond the name.

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 usage context: 'These overrides can be applied to other instances' implies when you'd want to use this tool (to copy overrides). However, it doesn't explicitly mention when not to use it or name the alternative tool 'set_instance_overrides', so it lacks exclusions.

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