capture_screenshot

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

No annotations provided, so description carries full burden. Only mentions return value, not behavioral traits like side effects, permissions, or whether it affects device state. Missing critical disclosure for a mutation tool.

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?

Single sentence, front-loaded with purpose, no fluff. Efficiently communicates main goal and return value.

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 simple screen capture with 2 params and no output schema, description adequately states purpose and output. Minor gap: no mention of image format or metadata structure, but not critical given tool simplicity.

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 covers both parameters with descriptions for deviceId and enum for platform. Description adds minimal value beyond schema; platform lacks explicit description but enum clarifies. Schema coverage 50% is compensated by schema itself.

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?

Clear verb ('Capture') and resource ('screenshot') with platform specification ('Android device or iOS simulator'). Returns device metadata and image, distinguishing from siblings like capture_debug_snapshot. Fully describes purpose.

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 for capturing screenshots, but no explicit guidance on when to use this tool vs alternatives like get_current_screen or capture_debug_snapshot. Lacks exclusions or context.

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