pricing__get_iap_price

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

Annotations already declare readOnlyHint and idempotentHint, but the description adds substantive context beyond them: it returns both current and scheduled prices with currency, customer price, proceeds, dates, and manual/automatic source. That tells the agent the read is richer than a simple scalar lookup.

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 short sentences, front-loaded with the operation and scope, then the two invocation forms, then the territory default. 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?

An output schema exists so return shape needn't be explained, annotations cover the safety profile, and the description covers the operation, resource, and both required invocation patterns. Nothing needed to call it correctly is missing.

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 the baseline is 3, but the description adds the mutual-exclusivity contract (IAP ID alone vs app + product ID) and the 'omit territory = all countries' default, which the schema does not state outright.

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+resource ('Read ... in-app purchase prices'), scopes it ('by territory'), and enumerates the returned fields. It is clearly distinguishable from the sibling readers pricing__get_app_price and pricing__get_subscription_price and the writer pricing__set_iap_price.

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?

Gives concrete invocation guidance: supply an IAP ID alone, or an app plus product ID, and omit territory to fetch every country. It stops short of explicitly stating when to prefer this over the app-price or subscription-price readers, so it is clear context without exclusion rules.

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