game_center_leaderboard_images_create_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 for a mutation tool, yet it discloses almost nothing: no auth/permission requirements, no note on what the body must contain beyond pointing at an external schema, no sense of side effects or reversibility. The DEPRECATED label is genuinely useful context, which keeps this above the floor.

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 brief and front-loads the DEPRECATED status, which is the most decision-relevant fact. But the endpoint is needlessly repeated in parentheses, and the sentence spends its remaining length deferring to an external spec instead of conveying a fact the agent needs.

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 creation endpoint with a required nested body object, no output schema, and no annotations, the description is too thin: it does not confirm what is returned, whether the resource is accessible afterward, or how it relates to the v2 sibling. The deprecation notice is the one piece of context an agent could act on.

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 the single body parameter is already documented, and the description merely repeats the same schema reference (components.schemas.GameCenterLeaderboardImageCreateRequest) without adding field-level meaning or JSON:API envelope guidance. Baseline 3 is appropriate when the schema does the work and the description adds nothing new.

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 identifies the operation via its HTTP verb and endpoint (POST /v1/gameCenterLeaderboardImages) and carries a DEPRECATED marker, so an agent can tell it creates a leaderboard image resource. However, it never states the resource in words and gives no basis to distinguish it from the sibling game_center_leaderboard_images_v2_create_instance, which matters given the near-identical v1/v2 pairs in this toolset.

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 tag is the only usage signal and it is buried in brackets rather than explained; there is no guidance on when to use this instead of the v2 create variant, nor any stated prerequisites or parent-resource requirements. An agent is left to infer routing 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.