game_center_leaderboard_set_localizations_delete_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. Deletion is irreversible and cascading effects, required permissions, and whether dependent localizations/leaderboards are affected are all unstated; the HTTP verb alone is the only behavioral signal.

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?

Extremely short and the deprecation notice is front-loaded, but the path is duplicated verbatim in parentheses, which is pure redundancy rather than earned content.

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 destructive, deprecated endpoint with no annotations and no output schema, the description is a stub: it never confirms irreversibility, deprecation replacement, or required permissions, leaving an agent without the context needed to invoke it responsibly.

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?

There is a single required 'id' parameter with 100% schema description coverage ('the id of the requested resource'), so the schema already documents it and the description adds nothing beyond it. Baseline 3 applies.

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 names the HTTP verb and the exact resource path (DELETE /v1/gameCenterLeaderboardSetLocalizations/{id}), so the operation is identifiable, but it is essentially a restatement of the tool name in path form and does nothing to distinguish it from the many sibling delete/localization endpoints.

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 only guidance is the [DEPRECATED] tag, which does warn the agent, but there is no statement of when this should be used versus the v2 variant (game_center_leaderboard_set_localizations_v2_delete_instance) or the parent collection tool, and no preconditions are given.

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