game_center_leaderboard_set_images_update_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. It discloses only that this is a PATCH (mutation) and that it is deprecated; it says nothing about required scopes, which fields are mutable, whether the change is reversible, or what happens to unmentioned fields. For a mutation with zero annotation coverage this is a significant 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?

A single front-loaded sentence with the deprecation warning first, which is the most important fact. The redundant parenthetical repeating the same PATCH path verbatim is wasted space, keeping it just short of a 5.

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?

This is a mutation tool with a nested, loosely-typed body object, no annotations, and no output schema. The description offloads the entire request shape to an external OpenAPI component and provides no replacement guidance, so an agent lacks enough context to invoke it confidently or to know it should not.

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%, so both parameters (id, body) are already documented in the schema. The description merely repeats the schema's pointer to components.schemas.GameCenterLeaderboardSetImageUpdateRequest without adding field-level meaning. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific HTTP verb and resource path (PATCH /v1/gameCenterLeaderboardSetImages/{id}), which uniquely identifies the operation against siblings. The [DEPRECATED] tag further distinguishes it from the live v2 update tool. It stops short of describing what the operation actually updates in business terms.

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 [DEPRECATED] marker signals 'avoid this', but there is no explicit redirect to a replacement, even though game_center_leaderboard_set_images_v2_update_instance exists among the siblings. No when-to-use condition, prerequisites, or alternatives are named.

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