imgui_load_font

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. 'Load... into the live ImGui atlas' implies a mutating operation, and the merge/size/glyph behavior is only implicit. It doesn't disclose error outcomes (e.g., failure on invalid path), whether the operation is reversible, overwrite behavior for duplicate IDs, or whether this modifies state globally.

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?

Two concise sentences with zero filler. The forward reference to imgui_set_font adds value without bloat. Could arguably add a bit more behavioral context, but for its length it is efficient and front-loads the core action.

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 font-loading tool with no annotations and no output schema, the description is thin on behavioral context. It doesn't mention error handling for invalid paths, ID collision behavior, or any persistence guarantees. The structured schema covers parameters well, but the overall tool semantics — especially side effects and requirements — are under-explained for an agent to invoke confidently.

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%, so all five parameters already have descriptive text in the schema (unique font identifier, native-app-visible path, merge for icon fallback, size with default, glyph preset enum). The description adds marginal value beyond the schema by framing the 'stable ID' concept, but doesn't elaborate further on parameter usage or format expectations. 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 verb+resource ('Load a TTF or OTF font into the live ImGui atlas under a stable ID') with a specific, distinct purpose. It distinguishes from the sibling imgui_set_font by noting the loaded font can then be made the global default, though it relies on that single reference rather than fully contrasting with imgui_list_fonts.

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 includes one usage pointer ('Use imgui_set_font to make it the global default'), which hints at the workflow. However, it doesn't explicitly address when to load a font vs. alternatives, prerequisites (e.g., that a window/app must be alive to load into the atlas), or when merging glyph_ranges would be appropriate beyond the param description.

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