game_center_leaderboard_set_images_v2_create_instance

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

No annotations are provided, so the description carries the whole burden, and it discloses nothing: not that this is a mutating write, not that the JSON:API envelope requires type/id/attributes, not upload/permission requirements or idempotency. It only echoes the endpoint signature.

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 path is repeated verbatim in parentheses, which is pure redundancy, and the only substantive content is deferred to an external reference rather than front-loaded. Not wasteful in length, but wasteful in content.

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?

A complex JSON:API creation endpoint with no annotations, no output schema, and an opaque body needs the description to explain the envelope and required fields. Pointing at an external OpenAPI component by name is the bare minimum and leaves the agent unable to construct a valid call from this definition alone.

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?

The single parameter is an opaque free-form object (`additionalProperties: {}`), so the nominal 100% schema coverage conveys no actual field information. The description's only contribution is pointing at the external name components.schemas.GameCenterLeaderboardSetImageV2CreateRequest, which is a lookup the agent may not have and does not explain required attributes like file name/size.

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 states the HTTP verb and resource path (POST /v2/gameCenterLeaderboardSetImages), from which an agent can infer that a new leaderboard set image is created. However, it never uses a plain-language verb like 'create' or says what the resource is; the intent is only recoverable by decoding the REST path and matching it against the tool name.

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 versus game_center_leaderboard_set_images_v2_update_instance, v2_get_instance, or the v1 game_center_leaderboard_set_images_create_instance sibling. No prerequisites, no mention that an existing leaderboard set localization/image relationship is required.

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