sassy_screenshot

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

With no annotations, the description must disclose side effects and behavior. It does explain monitor and region semantics, but fails to say what happens to the screenshot (e.g., saved to the 'path' parameter), whether it captures the entire screen, or what the output format is. This lack of behavioral disclosure is a significant gap.

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 short sentences, no fluff, and the action is front-loaded ('Take screenshot'). However, the parameter explanation is crammed into the second sentence, making it slightly dense. Still, it is concise and earns its place.

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?

For a relatively simple tool with an output schema, the description covers the core action and two of three parameters. The unexplained 'path' parameter and lack of information about default capture behavior leave gaps. It is adequate but not fully complete.

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 schema has zero parameter descriptions (0% coverage), so the description must compensate. It adds value by explaining the region format (x,y,w,h) and monitor values (-1 for all, 0 for primary, 1+ for others), but leaves the 'path' parameter entirely undefined. This partial compensation yields a baseline score of 3.

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 states 'Take screenshot', which is a specific verb+resource. It distinguishes this tool from sibling tools like sassy_click or sassy_screen_info, which have different purposes (clicking, screen info).

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 on when to use this tool versus alternatives such as sassy_screen_info or sassy_desktop_state. The description only explains parameters, not the context or exclusions for usage.

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