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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety bar is lower. The description adds a genuinely useful behavioral detail — the change is visible on the site within seconds — but never warns that existing ordering is overwritten or clarifies what happens when both sort_by and ids are supplied.

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?

A single front-loaded sentence with no filler; the 'site shows it within seconds' clause earns its place as timing context. Minor ambiguity in 'the site' keeps it short of perfect.

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?

Output schema exists so return values need no explanation. But with 5 parameters at 20% schema coverage, a destructive, non-idempotent tool should do more: descending direction and sort_by value domain are unaddressed, and the overwrite of prior ordering isn't stated.

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 only 20%, so the description does real work by explaining the key mutual-exclusion semantics (sort items by a field versus by given ids) and by noting the 'rest follow' behavior. However, it says nothing about 'descending', how 'sort_by' values are named, or what site/list expect, leaving several parameters undocumented in both places.

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?

States a specific verb and resource ('Sorts a list's items') and explains the two ordering modes: by a field or by explicit ids. That distinguishes it reasonably from update_list_items and add_list_items, though it never names those siblings.

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?

Usage is only implied: you infer you'd use it when you want a custom or field-based order. There is no explicit when-to-use versus update_list_items, no statement about what happens if ids don't cover all items (beyond 'the rest follow'), and no preconditions such as needing existing list permissions.

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