set_android_store_listing

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

Annotations already indicate a write operation (readOnlyHint=false, destructiveHint=false). The description adds valuable behavioral details: partial update, immediate effect, and no staging. This provides deeper insight beyond the annotation schema.

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?

Two concise sentences: first states purpose and key constraint, second adds behavioral note. No redundant or vague wording. Every sentence earns its place.

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?

Given no output schema, the description sufficiently covers update behavior, partial update, and immediate effect. It could optionally mention return value, but for a mutation tool this is adequate. Completeness is high for the tool's complexity.

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?

The input schema covers all parameters with descriptions (100% coverage). The description adds meaning by explaining the partial update semantics, which tells the agent that omitted fields are untouched. This is extra context beyond the schema.

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 'Update the Google Play store listing for a specific language,' which is a specific verb and resource. This differentiates it from siblings like get_android_store_listing (read) and upload_to_google_play (binary upload).

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 explicitly notes partial update behavior ('Only the fields you provide are updated') and immediate effect ('Changes go live immediately on commit; there is no staging step'). While it doesn't explicitly compare to alternatives, the context signals show a distinct sibling set.

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