reorder_pages

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

Annotations already declare openWorldHint=true and destructiveHint=false, so safety is partly covered. The description adds one useful behavioral detail: the list must be complete and ordered, implying full-replacement semantics rather than an incremental move. It does not state the consequence of omitting a page, permission needs, or the response.

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 zero filler, and the core operation is front-loaded before the calling constraint. Nothing could be trimmed without losing content.

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 one-parameter, non-destructive operation with no output schema, the definition covers what an agent needs to call it correctly: what it does and that the ID list must be complete and ordered. It is thin on failure behavior and permissions, but not inadequate at this complexity.

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 description ("Full ordered list of page IDs in desired nav order") already conveys the same information as the description's sentence. The description therefore adds no semantics beyond the structured field, which is the baseline-3 case for a single fully documented parameter.

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 (Reorder) and resource (pages in the website navigation), which is clearly distinct from siblings such as update_page, set_page_hidden, and list_pages. It does not explicitly name an alternative, but the operation is unambiguous.

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?

"Pass the complete ordered list of page IDs" is an invocation constraint rather than when-to-use guidance. There is no mention of prerequisites, when to prefer this over update_page, or what happens if the list is partial.

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