imgui_remove_callback

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

No annotations are provided, so the description carries the full burden. The description doesn't disclose what happens when no filter is provided (does it remove ALL callbacks?), whether removal is scoped to a window/scene, side effects of removal, or what success/response looks like. 'Remove' implies mutation but the destruction semantics are underspecified.

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?

One concise sentence, no waste, immediately states the purpose and the filtering capability. Could be slightly more informative but is appropriately terse.

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 2-parameter filter tool with zero required parameters and no annotations, the description should clarify edge cases (removal with no filters, interaction between filters, scoping). It's minimally adequate but leaves the all-removal and filter-combination semantics ambiguous, which an agent needs to know for a destructive operation.

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 both parameters have descriptions in the schema (Action type to remove, Trigger widget to remove callbacks for). The description restates that these are filters but doesn't add format/syntax details, wildcard behavior, or whether filters can be combined. 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 states a specific verb+resource ('Remove declarative callbacks') and mentions the two filtering parameters (trigger_widget and/or action). It's clear about what it does. However, it doesn't explicitly distinguish itself from the sibling imgui_set_callback (the counterpart), though the removal intent is clear enough.

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 says callbacks can be filtered by trigger_widget and/or action, which implies usage context (both parameters optional, filter-based removal). However, it doesn't explain when to choose this over alternatives, when all callbacks are removed (if neither filter given), or add/remove semantics relative to imgui_set_callback.

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