Reorder achievements

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

The annotations provide almost no positive safety information (all hints false), so the description carries the burden. It discloses that the operation is presentation-only, that omitted slugs keep their positions, and that the effect appears in both the game page and the SDK. This is meaningful behavioral context beyond the structured fields.

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?

The description is three sentences and every sentence contributes: effect, partial-order behavior, and ordering guidance. It is slightly longer than strictly necessary, but the final advisory sentence provides useful judgment guidance for choosing an order, so the length is justified.

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 mutation tool with no output schema, the description covers the behavior, the ordering semantics, and the presentation-only nature of the change. It does not mention permissions or idempotency, but the tool is simple enough that an agent can invoke it correctly from the given information.

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%, so the baseline is 3, but the description adds real semantic value by explaining that slug order is meaningful and that omitted slugs retain their prior positions. This goes beyond the schema's 'first to last' phrasing and helps the agent construct the right slugs array.

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 a specific verb and resource: it rewrites display order on the game page and in the SDK's achievements.list(). It clearly identifies this as achievement reordering, distinguishing it from sibling tools like reorder_screenshots without needing to state the alternative.

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 description gives clear context for use: you call it when you want to change achievement display order, and it explains the exact behavior of partial reordering. It does not explicitly mention alternative tools or when not to use it, but the scope is unambiguous enough that an agent can select it correctly.

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