cleanshot_scrolling_capture

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only says 'Open' and reveals nothing about side effects, whether a capture UI appears, whether auto-scroll is triggered, or what happens with the provided parameters.

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 with no wasted words. But it is so minimal that it reads more as an under-specified label than a helpful explanation.

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?

Given 7 optional parameters, no annotations, and no output schema, the one-sentence description is completely inadequate. It does not explain return values, prerequisites, how to use the parameters, or what 'Scrolling Capture mode' actually entails.

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?

The input schema has 100% coverage with individual descriptions for all 7 parameters, so the description does not need to repeat them. However, it adds no value about how parameters interrelate or how x, y, width, height, and autoscroll affect the scrolling capture mode.

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 action ('Open') and a specific resource ('CleanShot's Scrolling Capture mode'), which distinguishes it from sibling capture tools by naming the mode. However, it does not explain what the mode does or its scope beyond the name.

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 guidance is given about when to use this tool versus alternatives like cleanshot_capture_area or cleanshot_all_in_one. There is no mention of prerequisites, use cases, or exclusions.

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