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

Annotations already cover destructive/idempotent/openWorld, but the description goes further: it discloses the exact 409 failure conditions for system groups, warns that passing null silently moves pages out of a group while still reporting success, and notes the API returns no body on success along with the recommended follow-up call. This is rich 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?

Purpose is front-loaded in the first clause and every sentence carries information (destinations, restrictions, position semantics, response behavior). It is dense and delivered as one long run-on paragraph rather than structured sections, which slightly hurts scannability.

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?

With an output schema present, the description needn't explain return values, and it still notes the empty response body. For a 4-parameter mutation tool with a nested position object, the guidance on prerequisites, restrictions, and follow-up is complete enough for correct invocation.

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 baseline is 3. The description does add value: it frames group_id as the destination (never the current location), stresses relative_to_id must be a page id never a group id, and clearly marks position as optional-and-usually-omitted. Much of this overlaps the schema text, but the 'do not invent a position' guidance meaningfully sharpens intent.

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 (move/reorder) and resource (pages in the tab bar) with three explicit modes: into a group, out to the top level, or to a new position. This clearly distinguishes it from siblings like xtiles_update_page, xtiles_set_page_layout, or xtiles_move-like group tools.

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?

Explicitly says where to get view_ids/group_id (xtiles_get_project_structure), when to set group_id to a real id vs null, when to omit position (append is 'almost always' correct), and when position is warranted. It also names the exclusion cases (system-flag groups, pages already in a system group) and the resulting 409.

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