promote_google_play_release

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

Annotations are minimal (readOnlyHint=false, destructiveHint=false). Description adds significant behavioral context: explains promotion without re-uploading, effects of user_fraction, halting, and resuming. No contradiction with 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?

Three sentences: first states purpose, second explains user_fraction, third covers halt/resume. Front-loaded, no redundant words, efficient and clear.

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 all parameters (package_name implied by standard schema), explains promotion workflow, staged rollout, and edge cases (halt/resume). No output schema needed; context fully supports correct usage.

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?

Although schema coverage is 100%, description adds meaning beyond enum values: explains user_fraction as staged rollout percentage (0.1 = 10%), and how release_status and tracks interact for halt/resume. This is highly informative.

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 the tool promotes releases between Google Play tracks without re-uploading, using specific verbs and resource. It distinguishes from siblings like upload_to_google_play (which involves uploading) and set_rollout_fraction (focused on rollout fraction, not track promotion).

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 explicit when-to-use: for staged rollout set user_fraction, for halting set tracks to production and release_status='halted', for resuming set same tracks with inProgress and user_fraction. Gives clear alternative scenarios and parameter combinations.

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