imgui_set_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. It doesn't disclose whether this is a persistent/destructive change, whether it affects already-created windows/widgets, whether it's reversible, or any side effects on rendering. For a state-mutation tool with zero annotations, this is a notable gap.

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 sentences, zero wasted words. The critical edge case ('default' to restore embedded font) is front-loaded into the same sentence as the purpose. Exceptionally efficient.

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?

The tool is simple (1 param, no output schema), and the description covers the core semantics. However, for a state-mutation tool with no annotations, it would benefit from noting scoping (global vs per-window), persistence across redraws, or what visual effect to expect. Adequate for a simple tool but not rich.

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% (the single 'id' parameter is fully described as 'Loaded font ID or default'). The description adds the special 'default' value semantics, which is helpful, but doesn't explain what a 'loaded font ID' is beyond what the schema states. Description adds marginal value while schema covers the parameter adequately.

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: 'Set the global default font by loaded ID.' This distinguishes it from sibling imgui_load_font (loading) and imgui_list_fonts (listing), making the purpose 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 usage context: you set a font after loading it by ID, and 'default' restores the embedded font. However, it doesn't explicitly state when NOT to use it or name alternatives like imgui_load_font, so usage guidance is implied rather than explicit.

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