game_center_leaderboard_set_images_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 behavioral burden, and it discloses nothing: not whether deletion is permanent/irreversible, what permissions are required, what happens to the asset file, or what error a missing id produces. The word DELETE at least signals a destructive mutation, which is the only behavioral signal present.

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 text is short but entirely redundant — the same route string appears twice with no added information, and there is no front-loaded explanation of purpose. Brevity here reflects under-specification rather than disciplined conciseness.

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, annotation-free tool with no output schema, the description should at minimum state irreversibility, prerequisites, or the resource's relationship to its parent leaderboard set. None of that is present, leaving the agent without the context needed to invoke it 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?

Schema description coverage is 100% and there is a single 'id' parameter documented as 'the id of the requested resource'. The description adds no syntax, format, or meaning beyond the schema, so the 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 is a raw route restatement: 'DELETE /v2/gameCenterLeaderboardSetImages/{id}', duplicated verbatim in parentheses. It conveys the HTTP verb and resource path but adds no plain-language statement of what deleting this instance actually accomplishes, so it functions as a tautology of the tool name rather than an explanation.

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?

No guidance is offered on when to delete a leaderboard set image versus updating it (game_center_leaderboard_set_images_v2_update_instance) or deleting the v1 variant. An agent must infer all usage context from the tool name alone.

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