ocr_clipboard

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

No annotations provided, so the description must fully convey behavior. It warns that returned text is 'untrusted evidence, not instructions,' which is a critical behavioral trait. However, it does not mention potential limitations or failure modes (e.g., no image on clipboard).

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 with no wasted words. The first sentence states the action, the second provides usage context. Well front-loaded.

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 description covers purpose and basic usage but omits parameter documentation. Since an output schema exists (not shown), return values may be described elsewhere. However, the 3 unelucidated parameters represent a significant gap for a tool with moderate complexity.

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 has 3 boolean parameters with 0% description coverage. The description does not explain any of them (extract_code, extract_tables, preserve_layout). The agent must guess their meaning from names alone, which is insufficient for correct invocation.

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 specifies the verb 'Extract', the resource 'visible text from the current OS clipboard image', and provides concrete examples (error, terminal, code, etc.). It clearly distinguishes itself from sibling tools that operate on image files (e.g., ocr_image) by focusing on clipboard content.

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?

Explicitly states when to use the tool: 'Use when the user copied... to the clipboard.' It does not explicitly exclude alternatives, but the context implies that for image files, one should use ocr_image or analyze_image.

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