sassy_desktop_state

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

With no annotations, the description carries the full burden and does well: it discloses that coordinates are absolute across all monitors, names the underlying libraries, and flags the macOS permission need. It does not mention any additional side effects or limitations, but for a read-only state getter, this is reasonably transparent.

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?

Three sentences, each earning its place: first states the core purpose, second describes output style and coordinate system, third covers platform specifics. No fluff or repetition.

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?

Covers the essential functionality, output format, coordinate system, and platform-specific requirements. The only notable gap is not explaining the include_taskbar parameter, but the output schema likely handles return value details. Overall sufficient for an agent to invoke effectively.

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 0% description coverage and the description does not mention the include_taskbar parameter at all. The parameter name is somewhat self-explanatory, but the description fails to clarify its effect on output or why an agent would set it. Given the low coverage, the description should have compensated but did not.

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 the tool retrieves desktop state (open windows and positions), which is a specific verb+resource combination. It distinguishes itself from sibling tools like screenshots or screen info by specifying 'open windows and positions' and adds 'lean output' and coordinate system details.

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?

Provides clear context on when to use it by explaining platform-specific implementations (pywinauto on Windows, System Events on macOS) and the Accessibility permission requirement. However, it does not explicitly mention alternatives or when not to use this tool, so it stops short of full exclusion guidance.

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