imgui_clipboard

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

No annotations are provided, so the description carries full burden. It doesn't disclose whether 'set' can overwrite existing clipboard content silently, whether 'get' blocks or returns empty on failure, platform differences in clipboard behavior, or whether ImGui must be initialized first. For a tool with zero annotation coverage, 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?

Single sentence, zero wasted words, entirely front-loaded. It's efficient though arguably under-specified; still, for conciseness this is appropriately brief.

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?

A two-action tool (get/set) with no output schema and no annotations. The description doesn't cover return value for 'get' (is it a string? null on failure?), silent overwrite behavior for 'set', platform variance, or interaction with the ImGui context. For a tool that touches the system clipboard, more behavioral detail would help an agent know what to expect.

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%, and the 'action' enum already makes get/set semantics clear. The description adds the word 'text' which clarifies the data type of the clipboard content and the 'text' parameter. Baseline 3 is appropriate since the schema handles parameter documentation well.

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?

Description states 'Get or set the system clipboard text via ImGui' with a specific verb ('get or set') and resource ('system clipboard text'). It clearly differentiates from the many input/screenshot/window siblings. It doesn't name an alternative explicitly but the distinct clipboard resource makes 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?

No elaboration on when to use get vs set, when clipboard access is appropriate, or any context around clipboard integration with ImGui. No explicit exclusions or alternatives mentioned. The 'action' enum partially clarifies usage but the description adds no guidance.

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