game_center_leaderboard_localizations_v2_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 burden, yet it discloses nothing about the destructive nature, irreversibility, required permissions, or effects on related resources. A bare endpoint echo for a DELETE mutation is a serious 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 short, but the content is a verbatim repetition of the same endpoint string in parentheses, which is pure waste rather than useful structure. No information is front-loaded because there is essentially none.

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 delete tool with no annotations, no output schema, and no surrounding explanation, the description is completely inadequate. It leaves the agent without any of the behavioral context needed to invoke a mutation safely.

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 parameter (id) with 100% schema coverage, so the schema already documents it fully. The description adds nothing beyond the schema, which sets the baseline at 3.

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 merely restates the tool name as a raw HTTP endpoint ("DELETE /v2/gameCenterLeaderboardLocalizations/{id}"), duplicated in parentheses. It conveys a delete verb on a leaderboard-localization resource, but adds no explanation of what a leaderboard localization is or how this differs from the many sibling delete tools.

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 guidance on when to use this tool, no prerequisites, and no mention of alternatives such as the non-v2 sibling game_center_leaderboard_localizations_delete_instance or update_instance. The agent is left to infer everything from the name.

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