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

Adds real context beyond the readOnlyHint annotations: it discloses the data sources being compared (synced vs live public listing, tracked keywords, latest stored rank, cached Google demand), the constraints applied (store character limits), and the returned artifacts (drafts, coverage, opportunities, issues). Safety is confirmed ('read-only; never changes a store listing'). The openWorldHint (live public listing fetch) is implied but not called out as a latency/external-dependency caveat.

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?

Front-loads the trigger ('Use this when someone asks...'), then the two calling modes, then the return shape. The middle sentence is dense with a long compound clause but every element is substantive; nothing is 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?

An output schema exists, so return values needn't be enumerated, yet the description still gives the agent a mental model of the response (drafts fitting limits, coverage, opportunities, issues). With 8 all-optional parameters and 100% schema coverage, the remaining gap is the minimal one of not naming prerequisites for the check mode.

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%, so baseline is 3; the description earns above that by explaining the appId-omitted aggregate mode and the paired relationship (appId + store + proposed wording). It still leaves the store/country/language interaction and the one-per-line Microsoft keyword format to the schema, and doesn't mention that the proposed-wording check requires appId.

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 (suggest) and resource (store metadata: title, subtitle, keywords, short description), and names the ASO use case. It clearly distinguishes itself from siblings like get_store_metadata (retrieval) and list_keywords by framing the output as drafts plus opportunities/issues.

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?

Explicitly covers both modes: omit appId to cover every app in its main market ('for each app'), or pass appId/store with proposed wording to check your own copy. The conditional phrasing maps directly onto the tool's two calling patterns, leaving little to inference.

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