game_center_leaderboard_sets_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. It does disclose the substantive behavioral fact that the endpoint is deprecated (likely to be removed, a successor exists), which materially affects tool selection, but it says nothing about irreversibility, permission requirements, or cascading effects on related leaderboards.

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?

Very short and front-loaded, but the parenthetical repeats the identical path string verbatim, which is pure redundancy. The text is under-specified rather than genuinely concise.

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 omits the successor tool, the consequences of deletion, and any prerequisite context. An agent has enough to invoke it mechanically but not enough to decide whether it should.

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% for the single required 'id' parameter, so the schema already documents it fully. The description adds no format, sourcing, or constraint detail beyond what is in the schema, which is the expected baseline 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 restates the tool name in HTTP form: DELETE on /v1/gameCenterLeaderboardSets/{id}. The verb and resource are unambiguous, but it adds no scope or differentiation from the many sibling delete tools, notably game_center_leaderboard_sets_v2_delete_instance, which is never mentioned.

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 implies 'avoid this' but never says so explicitly, names no replacement, and gives no conditions for legitimate use. An agent must infer the alternative from the sibling list on its own.

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