List Google Play store listings

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

The annotations already declare readOnlyHint=true and openWorldHint=true, and the description reinforces this with an explicit statement that it creates, changes, and commits nothing. It also adds the prerequisite that an edit must already exist, which is real context beyond the annotations. It omits return shape or pagination details, but the read-only profile is well 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?

Two short sentences, with the scope statement front-loaded and the negative capability claim second. Nothing is redundant or padding.

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 simple two-parameter read tool with no output schema, the description covers what it returns (all localized listings) and the safety profile. The one meaningful gap is that packageName is undocumented in both the schema and the description.

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 description coverage is 0%, so the description must carry the meaning of both parameters. It explains editId only indirectly by tying it to "an existing app edit," and never mentions packageName at all, leaving the identifier's purpose and format entirely to the pattern in 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 uses a specific verb and resource ("Read all localized store listings") and scopes it to "an existing app edit". The phrase "all localized" implicitly distinguishes it from get_store_listing, which returns a single listing, so an agent can tell the two apart without opening either schema.

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?

It states the precondition ("Requires an editId") and rules out mutation ("does not create, change, or commit an edit"), which is genuine usage context. It never names an alternative such as get_store_listing or list_listing_images, or says when to choose this over them, so guidance is implied rather than explicit.

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