game_center_leaderboard_set_images_create_instance

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full behavioral burden, and it discloses only that this is a POST with a JSON:API body. It says nothing about authentication/permissions, what the image is attached to, whether the operation is reversible, or side effects. The deprecation note is the only real behavioral content.

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 phrase 'POST /v1/gameCenterLeaderboardSetImages (POST /v1/gameCenterLeaderboardSetImages)' is verbatim duplication that wastes the limited space. The [DEPRECATED] marker is correctly front-loaded, but the rest is machine-generated filler rather than a front-loaded purpose statement.

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 create/mutation tool with no annotations, no output schema, and a fully opaque body schema, the description is too thin: it defers the entire payload shape to an external OpenAPI component and omits auth, response, and replacement-endpoint information. Deprecation plus a schema pointer is not enough for an agent to invoke this 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 coverage is 100% for the single 'body' parameter, so the baseline is 3. The description's pointer to components.schemas.GameCenterLeaderboardSetImageCreateRequest is genuinely useful given the body schema is an empty additionalProperties object, but it merely duplicates what the property description already says, so it adds no meaning beyond the schema.

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 gives an HTTP verb and path (POST /v1/gameCenterLeaderboardSetImages), which implies 'create a leaderboard set image', and the [DEPRECATED] flag adds a useful status signal. However, it never states the purpose in natural language and gives no differentiation from the v2 sibling (game_center_leaderboard_set_images_v2_create_instance), which a deprecation marker arguably should point toward.

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?

Beyond the [DEPRECATED] tag there is no when-to-use or when-not-to-use guidance, no mention of a replacement endpoint, and no prerequisites. The deprecation warning implies 'avoid', but the agent is not told what to use instead, so routing remains ambiguous among the many game_center_leaderboard_set_images_* siblings.

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