set_visual_property

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

With no annotations, the description carries the full burden. It explains the meaning of objectName/propertyName, kind, and target, but does not disclose potential side effects (e.g., overriding existing settings), validation behavior, or whether changes are immediately applied or require a refresh.

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, dense with examples and parameter semantics, with no fluff. Every clause adds useful information, and the structure front-loads the core purpose.

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 tool's complexity (8 params, no output schema, no annotations), the description covers most key semantics and provides realistic formatting examples. It lacks details on error handling or return values, but the escape-hatch nature makes this acceptable. The sibling list reinforces its role as a generic setter.

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 63%, and the description adds significant value by providing concrete Power BI formatting id examples (labels/show, legend/position) and explaining target distinctions. It clarifies the 'kind' enum values and gives example values, going beyond the schema's terse descriptions.

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 ('Set') and resource ('ANY visual formatting property') while explicitly positioning it as 'the universal escape hatch.' This clearly distinguishes it from sibling tools like set_visual_format or set_visual_border, which target specific properties.

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 'universal escape hatch' phrasing implies use when no dedicated setter exists, and examples of object/property pairs clarify the target domain. However, it does not explicitly name alternatives or state when NOT to use it, leaving a slight gap.

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