imgui_set_safe_area

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

No annotations are provided, so the description carries the burden of disclosing behavior. The description states it sets pixel insets that anchored windows will respect, which gives reasonable behavioral context. However, it doesn't disclose what happens to windows already anchored (do they reflow immediately?), whether the change persists or is transient, whether it affects all windows or only future ones, or any interaction with viewport size. With zero annotation coverage, more behavioral disclosure would be warranted for a stateful configuration tool.

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, compact sentence: 'Set safe area insets (in pixels) that anchored windows will respect.' It front-loads the verbs and core purpose, and has no wasted words. It's appropriately minimal for a straightforward 4-parameter setter. Slightly more context could be added, but the current form is efficient and clear.

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 4-parameter setter with full schema coverage and no output schema, the description is minimally adequate. However, it omits key context: the meaning/range of values (can insets exceed viewport size?), whether unsetting/resetting is possible, and how this interacts with the many sibling layout tools (imgui_set_anchor, imgui_set_window_control, imgui_set_viewport_size). Given the tool sets state that affects window layout behavior, some additional context about scope and persistence would improve completeness.

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% with all four parameters (top, bottom, left, right) having clear descriptions ('Top inset in pixels' etc.). The description and schema together make the parameters self-explanatory. The description doesn't add extra semantics beyond what the schema provides, which places it at the baseline 3. No constraints like non-negative values or max bounds are indicated, but the schema itself is adequate.

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 what the tool does: 'Set safe area insets (in pixels) that anchored windows will respect.' It uses a specific verb (set) and identifies the exact resource (safe area insets) and the behavioral effect (windows will respect them). It doesn't explicitly name alternatives, but among the many imgui_* siblings, this configuration-focused purpose is distinct and clear.

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 the tool is used to configure the safe area that anchored windows respect, which gives context for when it would be used (when setting up window anchoring/layout). However, it doesn't describe when NOT to use it, what the defaults are if unset, whether this is a global or per-window setting, or how this relates to the sibling imgui_set_anchor / imgui_set_widget_anchor tools. Usage context is implied but not explicit.

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