imgui_unbind

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

With no annotations provided, the description carries full burden. It does disclose the 'remove all' behavior when both filters are omitted, which is a critical safety-relevant behavior. However, it doesn't disclose whether this is destructive/irreversible, what happens if no matching bindings exist, or error behavior on partial matches.

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, efficient sentence with zero waste. It front-loads the purpose and packs the filtering logic concisely. It could arguably be split into two sentences for readability but is well within acceptable length.

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-param, 0-required filter tool with 100% schema coverage and no output schema, the description covers the core usage. However, it doesn't confirm the delete is from the ImGui canvas, doesn't explain what 'bindings' refers to (presumably established via imgui_bind), and gives no post-condition information about what remains after removal.

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 the schema already documents both parameters as optional. The description adds 'Filter by source_widget and/or target_id, or omit both to remove all,' which adds filtering semantics and the combined-omission behavior. This does add value but the parameters are self-explanatory given their names.

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 clear verb ('Remove bindings') and resource (bindings), and distinguishes filtering options. It doesn't explicitly differentiate from the sibling 'imgui_bind' tool, but the inverse relationship is implicit in the name and the action is 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 gives context on how to use the tool: filter by source_widget and/or target_id, or omit both to remove all. This provides clear direction on invocation options, though it doesn't explicitly state when bindings exist or reference the binding creation counterpart.

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