imgui_set_resolution_preset

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It doesn't state whether this resizing is destructive to the current layout, whether it affects DPI or scaling, whether it persists across frames/animations, or what happens to existing windows/widgets when the viewport shrinks (e.g., from 4k to mobile). For a resize operation, these are meaningful behavioral concerns.

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?

One clear single sentence, zero waste. Front-loaded with the action verb. No filler or 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?

The tool is simple (1 required param, no output schema), so the bar for completeness is lowered. However, with no annotations and no behavioral disclosure about side effects on the scene/layout, the description leaves the agent uncertain about whether this is safe and what consequences resizing has on existing content. Adequate but with room to add safety/behavioral context.

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 preset enum itself documents all 7 valid values with a description ('Resolution preset name'). The description mentions 'common resolution preset' which aligns with the enum, but doesn't add conversion details like which presets are portrait vs landscape or actual pixel dimensions. Baseline 3 is appropriate since the schema covers the parameter fully.

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 'Resize the viewport to a common resolution preset' clearly states the verb (resize), resource (viewport), and scope (common resolution preset). It distinguishes from imgui_set_viewport_size by focusing on presets rather than arbitrary dimensions, though it doesn't explicitly call out that alternative.

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 when to use this tool (when you want a preset resolution rather than a custom size), but doesn't explicitly state 'use imgui_set_viewport_size for custom sizes' as a contrast. Given there is a sibling imgui_set_viewport_size doing related work, an explicit when-not statement would strengthen this.

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