Add an achievement localization

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

Annotations are absent, so the description carries the full burden of behavioral disclosure. It only says 'Add,' which implies a mutation, but it does not disclose whether duplicate locales are rejected, whether existing localizations are overwritten, what permissions are required, or what the API returns. This is a meaningful gap for a create/mutation tool.

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, front-loaded sentence with no wasted words. It immediately identifies the action, target, and scope. It earns its place and does not repeat the title verbatim.

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?

This is a simple creation tool with five fully documented parameters in the schema, so the description plus schema gives an agent enough to make a correct call. The lack of an output schema and minor behavioral gaps are noticeable but not crippling given the tool's simplicity and the high schema coverage.

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 the baseline is 3. The description adds no extra meaning beyond what the schema already provides for name, locale, versionId, and the two description fields. It maps generally to 'localized name/description' but does not clarify formats or constraints 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?

The description clearly states a specific action ('Add') on a specific resource ('localized name/description for an achievement version') and scopes it to 'one locale.' This distinguishes it from sibling tools like create_game_center_achievement or create_game_center_leaderboard_localization without requiring the agent to open the 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?

The description provides clear context: this tool is for adding a localization to an existing achievement version, for a single locale. It does not explicitly name alternatives or state when not to use it, but the target entity and scope make the intended use reasonably apparent. It lacks explicit exclusions or 'use X instead' guidance.

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