xcresult_get_screenshot

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

No annotations provided, but the description discloses use of ffmpeg and includes a warning in the timestamp parameter about choosing a time before failure to avoid capturing the home screen. However, it omits potential issues like ffmpeg availability 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?

Single sentence with key action front-loaded, no wasted text.

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?

Core purpose and key usage tip provided, but no mention of output format (e.g., base64 image, file path) despite no output schema. Could be more complete.

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 has 100% description coverage, and the description adds value beyond the schema by explaining the timestamp warning in detail and mentioning ffmpeg usage.

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?

Description clearly states it gets a screenshot from a failed test at a specific timestamp using ffmpeg, distinguishing it from sibling tools like xcresult_export_attachment (exports raw attachments) and xcresult_get_ui_element (gets UI element info).

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 extracting a screenshot from a test failure video, but no explicit when-to-use, when-not-to-use, or alternatives mentioned.

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