cleanshot_open_history

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 the action without explaining side effects, prerequisites (e.g., CleanShot must be running), or what the user sees after opening history. This is a minimal description with no additional context.

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, focused sentence with no waste. It conveys the core action and object efficiently, making it exactly as concise as needed for a parameterless tool.

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 the tool's simplicity, the description is adequate but not fully complete. It lacks context about what 'capture history' displays and how it relates to similar siblings like 'restore_recently_closed'. This could lead to ambiguity, so a more contextual explanation would improve completeness.

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?

There are zero parameters and the schema is empty. According to the rubric, 0 params yields a baseline of 4. The description does not need to explain parameter details since none exist, and no gaps are present.

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 'Open CleanShot's capture history' uses a specific verb and resource, clearly distinguishing it from sibling tools like 'open_settings' or 'open_annotate'. However, it could more explicitly state what 'capture history' entails (e.g., a list of recent screenshots) to fully avoid ambiguity.

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 about when to use this tool versus alternatives. The description does not mention exclusions or compare with siblings such as 'cleanshot_restore_recently_closed', leaving the agent without enough context for tool selection.

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