cleanshot_record_screen

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. It only states 'Open CleanShot's Record Screen mode', which is ambiguous—it could mean launching a UI or immediately starting a recording. No mention of side effects, permissions, or whether the recording saves automatically leaves the behavior opaque.

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, front-loaded sentence with no unnecessary words. It is appropriately sized for its purpose, though it could include more contextual detail without becoming verbose.

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 tool has 5 optional parameters defining a recording area and no output schema or annotations. The description does not explain how these parameters relate to the recording mode, what happens after opening, or when to use this over sibling tools. This is a significant gap for a potentially complex operation.

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 documents all 5 parameters with descriptions (100% coverage), so the baseline of 3 applies. The tool description itself adds no additional parameter semantics beyond the schema, but the schema already provides sufficient meaning for each parameter.

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 uses the specific verb 'Open' with the resource 'Record Screen mode', clearly identifying the tool's function and distinguishing it from sibling capture tools like cleanshot_capture_area. However, it is minimal and does not elaborate on the recording behavior, which prevents a perfect score.

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 provided regarding when to use this tool versus alternatives such as cleanshot_capture_area or cleanshot_capture_fullscreen. The description gives no context on use cases, prerequisites, or exclusions, leaving the agent without selection criteria.

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