Get In-App Purchases

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful context about localization and the 'top' qualifier, but provides no additional behavioral details (e.g., pagination, limits). This aligns with the calibration example for get_calls.

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?

The description is a single well-structured sentence of 14 words. It is front-loaded with the primary action ('Get'), clearly states the target resource, and includes relevant output characteristics without unnecessary detail.

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 the presence of a complete input schema, output schema, and annotations, the description is fully adequate. It specifies the purpose and important output details (localized names and prices), leaving no critical gaps for an agent to misuse the tool.

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%, with both `id` and `country` fully described. The description adds marginal value by implying country affects localization and price formatting, but the schema already provides the necessary semantics for both parameters.

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 the tool gets 'top in-app purchases shown on an app's App Store page' and specifies 'localized names and formatted prices.' This is a specific verb+resource combination that distinguishes it from sibling tools like app_store_reviews or app_store_app.

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 provides clear context: it is for the top in-app purchases on an app's App Store page. It does not explicitly name alternatives or exclusion conditions, but the purpose is unambiguous relative to the sibling tool names.

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