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

Annotations only say non-read-only and non-destructive; the description goes well past that by spelling out that the move is IN PLACE and that id, section ids, layouts, copy, backgrounds and slug are untouched. It also discloses two behavioral traps (root page, blog-named pages) that the annotations cannot express.

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?

Four tight clauses, front-loaded with the core action and the scope of the change, followed by the two edge cases. Nothing repeats the tool name or restates the schema without adding meaning.

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 three-parameter mutation with no output schema, the description covers what changes, what is preserved, and the main invalid inputs. It does not say what happens if pageName is not found or what the call returns, which would round out failure handling.

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 0%, so the description must carry the weight. It usefully enumerates the category values and ties pageName semantics to the blog-group constraint, compensating for the undocumented enum meaning. projectId is never mentioned, which keeps it from a 5.

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?

Opens with a specific verb plus resource and scope: 'Move a page to another group of the sitemap.' It enumerates the five valid groups and distinguishes itself cleanly from uichemy_rename_page and uichemy_reorder_pages by stating only the group changes.

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?

Gives explicit preconditions and exclusions: the home page is the root and cannot be moved, and blog-named pages must be renamed first. It stops short of naming the alternative tool (uichemy_rename_page) directly, leaving the agent to infer which tool to call for that workaround.

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