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 and behavior. 'Get' implies a read-only operation, but the description does not explicitly state that it makes no modifications or disclose any side effects, permissions, or return format details. It adds the context that overrides can be applied elsewhere, but this is more about usage than tool behavior.

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 concise sentences with no redundant information. The first states the core function, the second explains the value of the output. Excellent front-loading.

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 low complexity (one optional parameter, no output schema), the description covers the essential purpose and usage. It lacks explicit return structure details, but this is a simple getter and the sibling set_instance_overrides implies how the result is used. Slightly more detail on the output would make it fully complete.

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?

The schema already documents the single optional parameter nodeId with a clear description, so schema coverage is 100%. The description adds no further meaning about the parameter, thus the baseline score of 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 clearly states 'Get all override properties from a selected component instance' with a specific verb and resource. It also explains the purpose of the overrides (applying to other instances), distinguishing this getter tool from its sibling set_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?

The description implies the usage context: retrieve overrides so they can be applied to other instances. This suggests the workflow of getting then setting overrides, though it does not explicitly name set_instance_overrides or state when not to use this tool.

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