game_center_leaderboard_localizations_get_instance

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

No annotations are provided, so the description carries the full behavioral burden, and it delivers almost nothing: the HTTP verb implies a read-only fetch, and the deprecation flag warns against use, but there is no mention of permission requirements, whether the resource returns 404 for stale IDs, or any lifecycle guidance. For a tool with zero annotation coverage this is a substantial gap.

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?

It is a single short line with the deprecation warning front-loaded, so it is not padded or wasteful. However, its brevity reflects under-specification rather than disciplined conciseness, so it lands at adequate rather than strong.

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 five parameters, no annotations, and no output schema, the description should at minimum explain that it fetches one localization by ID and whether the response is deprecated in favor of v2. It supplies only a repeated path and a deprecation flag, which is not enough context for an agent to invoke this confidently.

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% — all five parameters (id, include, and the three sparse-fieldset params) are documented in the schema itself. The description adds no parameter meaning whatsoever, so the baseline 3 for high-coverage schemas is the correct ceiling here.

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 is essentially a restatement of the tool name and its URL path ("GET /v1/gameCenterLeaderboardLocalizations/{id}"), which is tautological rather than explanatory. It does add one genuinely useful signal — the [DEPRECATED] tag — but never states in plain language that it retrieves a single leaderboard localization resource, nor distinguishes it from the sibling v2 variant.

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?

There is no explicit when-to-use guidance. The [DEPRECATED] marker weakly implies an agent should prefer a newer alternative, but the description never names that alternative (e.g., game_center_leaderboard_localizations_v2_get_instance) or states any precondition for calling this one. The routing signal is only inferable, not stated.

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