imgui_show_about

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

No annotations are provided, so the description carries full behavioral burden. It mentions the toggle nature ('Show or hide') and content ('version info, credits') but doesn't disclose side effects, whether the visible state is tracked, or what happens when shown repeatedly. Minimal disclosure beyond the obvious.

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 concise sentence that efficiently captures the tool's purpose with zero waste. Every word earns its place.

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 1-param boolean toggle tool with no output schema and no annotations, the description is functional but thin. It doesn't clarify how visibility state is managed relative to other window visibility tools (imgui_set_window_visibility), nor whether the about window is a distinct managed entity. Given the large sibling set with similar show_* tools, more context would help disambiguation.

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% — the 'show' parameter is described as 'Whether to show the about window', which matches the description's language. Baseline 3 is appropriate since the schema already handles parameter meaning adequately and the description doesn't add extra nuance beyond it.

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 verb (show/hide) and resource (ImGui about window) with the content context (version info, credits). It distinguishes from siblings like imgui_show_demo and imgui_show_metrics by naming the specific about window, though it doesn't explicitly contrast those tools.

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 vs alternatives like imgui_show_demo, imgui_show_metrics, or imgui_show_style_editor. The toggle semantics (show OR hide based on boolean) are implied by the parameter but not explicitly explained, and there's no mention of whether this toggles an existing state or sets it absolutely.

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