projector_screenshot

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

Annotations declare readOnlyHint=true, but the description says 'save it locally', which creates a file and is a write side effect inconsistent with read-only semantics. The description also gives no details about overwrite behavior, permissions, or error handling.

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 filler. It is appropriately sized for a low-complexity screenshot 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?

The schema covers the sole parameter and the annotations cover safety/open-world context, so the basic shape is complete. However, the description omits alternative-selection guidance and does not reconcile the local file write with the readOnlyHint=true annotation.

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 only parameter, 'output', is fully described in the schema with its default path, so schema coverage is 100%. The description adds only 'save it locally' and does not provide path or format details beyond what the schema already supplies.

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 states a specific verb ('take a screenshot') and resource ('projector screen'), plus local saving. It is clear, but it does not explicitly distinguish this from sibling screenshot tools such as screenshot_full, screenshot_monitor, or screenshot_to_clipboard.

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?

There is no guidance on when to use this tool versus the many other screenshot tools or projector tools. An agent must infer that it is specifically for the projector screen rather than a generic monitor/full-screen capture, and no alternative is named.

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