Capture paired Android displays

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the description does not need to repeat those. It adds the behavioral trait of tight pairing and same-moment capture, but does not disclose potential side effects (e.g., artifact creation, timing guarantees) or the non-idempotent nature beyond annotations.

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?

A single sentence with a parenthetical clarification conveys the core purpose efficiently. Every word earns its place, and the structure is front-loaded with the action and resource.

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 description captures the essence but omits important context: the meaning of 'display resolve', the output format (despite an output schema), and the behavior of saveArtifact. Given the tool's complexity and low schema coverage, a more complete description would improve usability.

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 low (33%), yet the description adds no parameter-level context. It does not explain the serial requirement, the meaning of displayIds, or the saveArtifact parameter. The agent must rely solely on the schema, which is insufficient for proper invocation.

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 ('capture'), the resource ('multiple logical displays'), and the unique value proposition ('tightly paired same-moment screenshots'). It distinguishes from sibling tools like mobile_screen_capture (single display) and mobile_screen_record (video). The parenthetical clarification reinforces the parallel, synchronized nature.

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?

The description implies usage for capturing multiple displays simultaneously but does not explicitly state when to use this tool vs. mobile_screen_capture or mobile_screen_record. No when-not-to-use guidelines or prerequisites are provided.

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