app_store_geo_search

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds nothing behavioral—no pagination limits (pageSize max 200), no explanation of what 'soft-blocked' means for the eligible flag, and 'eligible' in the description mildly conflicts with the fact that filtering is opt-in via the eligible parameter.

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?

A single front-loaded sentence with no padding. It is short to the point of omitting context an agent would want, but nothing is wasted.

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?

With 8 params at full schema coverage, an output schema, and annotations present, the structured data carries most of the load. The description is still thin on usage context and on the semantics of the eligible/countryCode filters, which is the remaining gap.

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 100%, so all eight parameters are already documented, giving baseline 3. The description restates three of the entity types but adds no syntax, defaults, or interaction details (e.g., how countryCode interacts with query) 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?

States a specific verb ('Search') and resource ('App Store countries, administrative areas, and localities'), which maps directly to the entity parameter values. No sibling tool covers geo search, so differentiation is implicit rather than stated, and the word 'eligible' slightly muddies scope since eligibility is actually opt-in via a parameter.

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?

No guidance on when to use this vs. related lookups (campaign_countries_preview, apps_eligibility, category_suggestions), no mention of the two required parameters being prerequisites (profile, adAccountId), and no note on the minimum query length rule beyond the schema.

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