imgui_set_style

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

No annotations are provided, so the description must carry the behavioral disclosure burden. The description states it applies a style theme but does not disclose whether this mutates persistent state, whether the change is reversible, whether it affects future widget rendering, or whether custom color overrides can be combined with a theme simultaneously. For a state-setting operation with zero annotation coverage, key behavioral details are missing.

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 a single concise sentence that clearly states the primary purpose and mentions the color override capability. It is appropriately short with no wasted words, though it could be slightly more specific about the behavior details without becoming verbose.

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 presence of nested colors objects (custom override map with specific array format), the description gives only a high-level mention of 'custom color overrides' without elaborating on the structure. However, the schema fully documents the colors parameter format (additionalProperties with 4-element number arrays), so the schema partially compensates. The tool has complexity (2 themes-related siblings like imgui_set_theme, imgui_set_style_var, imgui_push_style_color) and the description doesn't distinguish these, leaving the completeness gap significant.

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% — both theme (with enum values dark/light/classic and 'Built-in theme to apply') and colors ('Custom color overrides as a map...') are documented in the schema. The description adds the notion of theme selection and the custom override option but doesn't add meaningful detail beyond the schema. The baseline 3 is appropriate since the schema fully covers parameters.

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 'Set the ImGui style theme' with specific verb 'Set' and resource 'ImGui style theme', and enumerates the built-in themes (dark, light, classic) plus the custom override option. However, siblings like imgui_set_theme, imgui_set_theme_color, imgui_set_style_var, and imgui_push_style_color overlap in the styling space, and the description doesn't differentiate this tool from those set-related siblings.

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 explicit guidance on when to use this tool vs. alternatives. Siblings include imgui_set_theme, imgui_set_theme_color, imgui_set_style_var, and imgui_push_style_color — all in adjacent styling territory — yet the description says nothing about when to prefer this tool or how it differs from those. The context of custom color overrides implies use cases, but there's no explicit when/when-not guidance.

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