arc_take_screenshot

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

No annotations provided, description does not cover permissions, blocking behavior, return value, or cancellation. Lacks details about whether user interaction is required or how long it may take.

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 redundancy. However, could be structured better (e.g., list modes). Still concise and front-loaded.

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?

Adequate for a simple 2-param tool with no output schema. Missing behavioral context (e.g., does it require user interaction? What is the output?).

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 coverage 100% (both parameters have descriptions in schema). Description repeats mode values (range selection, window selection) which are already in schema. Does not add new semantic value beyond schema.

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?

Stated verb 'take screenshot' and resource (screen) clearly. Differentiates between two modes ('selection' and 'window'), making the action specific. No sibling tool duplicates this functionality.

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?

IMPLIED usage: user selects mode interaction type. No explicit when-to-use/alternatives, but no alternative screenshot tool exists among siblings, so context is adequate.

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