Reorder screenshots

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

The description discloses important behavioral details not available from annotations: omitted screenshot ids keep their relative order at the end, unknown ids are ignored, and the first listed id determines the lead image. There is no contradiction with the annotations, though return behavior and failure modes are not mentioned.

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?

Two sentences deliver the core behavior, ordering rule, fallback handling, and user-visible effect with no filler. The most important information is front-loaded.

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 two-parameter reorder operation with fully described schema inputs, the description covers the main call semantics and edge cases around omitted and unknown ids. It does not describe the response format, but no output schema exists and the mutation result shape is likely not required for tool selection.

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 schema already describes both parameters, giving a baseline of 3. The description adds meaningful semantics for screenshotIds by explaining ordering, omission behavior, and unknown-id handling, going beyond the schema's 'most important first' label.

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 names the verb 'reorders' and the resource 'a game's gallery', and clarifies the ordering intent with a concrete user-facing consequence: 'The first screenshot is the one people see first.' It is clearly distinct from sibling tools such as add_screenshot, remove_screenshot, and reorder_achievements.

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?

It is clear this tool should be used when the goal is to change the display order of a game's screenshots, and the description explains how the ordering works. It does not explicitly name alternatives or state when not to use it, so it stops short of a 5.

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