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

Adds real context beyond annotations: empty store fields preserve current values (partial-update semantics), the fetch reaches an external store (consistent with openWorldHint), and there is a one-per-minute-per-site throttle. It does not say whether failures surface as errors or what happens if the site is already in sync, but the key risks are covered.

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 compact sentences, front-loaded with the action, then the field-preservation rule, then the throttle. No filler.

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?

For a one-parameter mutation with annotations and no output schema, this covers what is refreshed, what is preserved, and the rate limit. The only gap is whether the response reports which fields actually changed.

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% and the single 'site' parameter is fully documented with accepted address formats and a pointer to list_my_sites. The description adds nothing about the parameter, which is acceptable given the schema does the work.

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?

States a specific verb ('Re-read ... now') and resource (the site's app metadata from Google Play or the App Store) plus the exact fields affected (name, icon, screenshots, description, what's new). This distinguishes it from update_site, which implies manual field edits.

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 word 'now' and the store-source framing make clear this is the sync-from-store path rather than manual editing, and the rate note ('Once a minute per site') tells the agent when it will fail. It stops short of explicitly naming update_site as the alternative or stating exclusions.

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