take-screenshot

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

With no annotations provided, the description carries full burden but only states the basic action without disclosing behavioral traits. It doesn't mention permissions needed, whether it requires an active device session, potential side effects (e.g., screen changes), or output handling (e.g., file saved locally). This leaves significant gaps for a tool that interacts with hardware.

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, efficient sentence with zero waste—it directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 tool that performs a hardware interaction (taking a screenshot on an Android device) with no annotations and no output schema, the description is incomplete. It lacks details on behavioral context, error handling, or what happens after execution (e.g., success confirmation, file format). Given the complexity and sibling tools, more guidance is needed.

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 parameters 'deviceId' and 'outputPath' are fully documented in the schema. The description adds no additional meaning beyond implying the screenshot is saved to a local path, which is already covered. Baseline 3 is appropriate as the schema does the heavy lifting.

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 action ('take a screenshot') and target ('on an Android device'), providing specific verb+resource. However, it doesn't differentiate from sibling tools like 'appium-screenshot' or 'xcode_take_screenshot', which appear to serve similar purposes on different platforms or contexts.

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 like 'appium-screenshot' or 'xcode_take_screenshot' from the sibling list. The description lacks context about prerequisites (e.g., device connectivity) or exclusions, offering minimal usage direction.

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