list_subscription_localizations

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It only says 'List', implying a read operation, but doesn't mention whether it returns all localizations, pagination, sorting, or any access requirements. This is a significant gap for a tool with no annotation support.

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 one short sentence with no unnecessary words. It is front-loaded and easy to parse. However, it is slightly under-specified for a tool with no annotations, so it doesn't earn a 5.

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 one-parameter read tool, this is a minimum viable description: it states what the tool does and the target. But it lacks behavioral details, return value expectations, and any usage context beyond the obvious. It's adequate but with clear gaps.

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?

The input schema already fully describes subscriptionId as 'The subscription ID' (100% coverage). The description adds minimal semantic value beyond restating that localizations are 'for a subscription', which is redundant. Baseline of 3 is appropriate.

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 ('List'), resource ('localizations'), and clarifies the target ('for a subscription'), while also describing what localizations are ('display names, descriptions'). This clearly distinguishes it from sibling tools like list_iap_localizations and set_subscription_localization.

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 clearly implies the context: use this when you need localizations for a specific subscription. However, it doesn't explicitly state when not to use it or mention alternatives, such as list_iap_localizations for in-app purchases or set_subscription_localization for updating.

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