transform_lofi_to_hifi

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

With no annotations present, the description carries the full burden of behavioral disclosure. It reveals the transformation intent and token application, but does not state whether the original artboard is mutated in place or a new artifact is created, whether the operation is reversible, or what side effects applying design tokens may have.

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 entire description is one efficient sentence that front-loads the core transformation and includes the key qualifier about design tokens. There is no filler or repetition of the tool name.

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?

The absence of an output schema and annotations means the description should explain the result and side effects, but it only describes the high-level transformation. It does not clarify what the caller receives, whether the source artboard is preserved, or how fileId/theme affect execution, leaving important operational context missing.

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 description coverage is 100%, so the baseline is 3. The description confirms that artboardId refers to the low-fidelity input, but it adds little detail beyond the schema about theme selection, optional fileId, or how these interact with active design tokens.

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 names a specific action ('Upgrades'), a precise input type ('low-fidelity wireframe or mockup artboard'), and a concrete outcome ('polished, high-fidelity production screen'). This makes it readily distinguishable from siblings like create_artboard or generate_theme_variant.

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 intended use case is implied: select this when a low-fidelity wireframe or mockup needs to become a high-fidelity screen. However, there is no explicit when-not-to-use guidance or comparison to sibling tools that might also alter design fidelity, such as generate_theme_variant or update_styles.

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