take_system_screenshot

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

Discloses cross-platform tools, default save location (~/Documents/screenshots), configurable via environment variable, and mentions outputPath parameter. No annotations exist, so description carries full burden. Adequate but does not explicitly state read-only nature or permissions.

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 concise sentences with no wasted words. Front-loaded with main action ('Capture desktop, window, or region screenshot'). Efficient and easy to parse.

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?

No output schema, so description should explain return value (e.g., file path). Does not mention what is returned. With 9 parameters and no output schema, more context on return format or side effects 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?

Schema description coverage is 100%, so the schema already documents each parameter. Description adds marginal value by explaining default output directory and cross-platform tools. Baseline 3 is appropriate.

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 'Capture desktop, window, or region screenshot' with specific verbs and resources. It distinguishes from the sibling tool 'take_screenshot' by implying system-level capture with cross-platform details and output directory.

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 guidance for window mode (needs windowName or windowId) and mentions cross-platform tools, but does not explicitly state when to use this tool versus the sibling 'take_screenshot'. Lacks when-not-to-use or alternatives.

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