imgui_show_demo

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

No annotations are provided, so the description carries the behavioral disclosure burden entirely. It does reveal the tool toggles a demonstration window, which implies a visual UI action rather than data mutation, but it doesn't disclose side effects, performance implications, or whether this is persisted across snapshots/scenes.

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?

A single sentence that efficiently conveys the purpose with zero wasted words. The parenthetical about showcasing widgets is genuinely informative for understanding what the window displays.

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 toggle tool with one boolean parameter and no output schema, the description is reasonably complete. However, it doesn't clarify how show=false behaves (hides window), whether the state persists, or any interaction with scene/window management siblings. Given the low complexity, this is adequate but not exceptional.

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% with a single boolean 'show' parameter already described ('Whether to show the demo window'). The description mentions showing/hiding which aligns, but adds no additional meaning beyond the schema's own parameter description. Baseline 3 is appropriate given full schema coverage.

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 the tool shows/hides the ImGui demo window and mentions it showcases all available widgets. It uses a specific verb (show/hide) with a clear resource (demo window), though it doesn't explicitly distinguish from siblings like imgui_show_metrics or imgui_show_about beyond the window 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?

No guidance on when to use this tool versus alternatives. There are sibling tools like imgui_show_metrics, imgui_show_about, and imgui_show_style_editor that also control debug window visibility, but the description doesn't address when the demo window is preferred or any caveats.

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