cleanshot_capture_text

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

No annotations are present, so the description carries the full burden. It fails to disclose what happens after text is recognized (e.g., copied to clipboard), how the result is returned, or any side effects like UI launching or clipboard modification. The linebreaks parameter hints at clipboard behavior, but that is in the schema, not the description.

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 concise sentence that communicates the primary functionality without extraneous words. It earns every word, maintaining a clear subject and two direct verbs.

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?

With 7 parameters, no output schema, and no annotations, the description is too brief to fully explain how parameters interact (e.g., screen capture vs file mode), what the output looks like, or any behavioral outcomes. The schema covers parameter descriptions, but the overall context remains incomplete for an agent to confidently invoke the tool.

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% for all 7 parameters, providing clear explanations of coordinates, display, filepath, and linebreaks. The description adds no additional parameter context beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 identifies the tool as CleanShot's Text Recognition (OCR) feature, with two distinct actions: opening the OCR tool or extracting text from a file. It is specific enough to distinguish from sibling capture tools, though it does not explicitly name alternatives.

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 for OCR but does not explicitly state when to use it vs. other capture tools, nor does it provide exclusions or prerequisites. The dual nature (open tool or extract from file) gives some context, but no direct guidance on parameter combinations or when to choose one mode over the other.

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