reorder_pages

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

Annotations declare destructiveHint=false, and the description adds meaningful behavioral context beyond that: the operation replaces the full navigation order, since a complete list must be supplied. It could go further by explaining what happens to omitted pages or what response is returned, but it covers the crucial mutation semantics.

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 short sentences with no filler. The purpose is front-loaded and the critical constraint ('complete ordered list') is stated immediately afterward.

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 simple one-parameter mutation with annotations and a fully documented schema, the description is nearly complete. It does not mention retrieving the current page list via list_pages or what happens on success, but those are minor gaps for this operation.

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%, and the schema already describes page_ids as the 'Full ordered list of page IDs in desired nav order.' The tool description mostly restates that requirement, adding little semantic value beyond what the schema provides.

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?

Description uses a specific action ('Reorder') and a clear resource ('pages in the website navigation'), so an agent can immediately identify what the tool does. The complete-list requirement also helps distinguish it from related page tools like update_page or set_page_hidden.

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 clearly states the key usage condition: the agent must pass the complete ordered list of page IDs, not a partial diff. It does not explicitly name alternatives or say when not to use this tool, but for a single-purpose reorder tool the context is clear enough.

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