upload_android_screenshots

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

Discloses atomicity of uploads, supported formats (JPEG, 24-bit PNG), max file size (8 MB), and that replace=true deletes existing screenshots. Annotations confirm readOnly=false and destructiveHint=false, with no contradictions.

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?

Five sentences, front-loaded with the main action, then constraints and recommended usage. Every sentence adds necessary detail without redundancy.

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?

Covers purpose, constraints (format, size, limit), atomicity, and replace behavior. No output schema needed as tool likely returns status; description is sufficient for an agent to invoke correctly.

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 is 100%, but description adds value by noting screenshot_urls are in display order, replace=true deletes all existing, and lists common image_type values beyond the schema's enum-like list.

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 explicitly states the tool downloads screenshots from URLs and uploads them to Google Play for a specific language and device type. This clearly distinguishes it from siblings like upload_ios_screenshots.

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?

Provides specific guidance on the 8-screenshot limit, replace=true recommendation, and listing common image types. Does not explicitly state when not to use but offers clear context for typical scenarios.

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