reorder_pages

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

No annotations are provided, but the description discloses key behaviors: assigning fresh ordinals, appending unlisted pages in relative order, and accepting page names or displayNames. This goes beyond a simple 'reorder' and gives the agent a clear model of the operation's effect.

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?

The description is two sentences, front-loaded with the primary action, and contains no filler. It efficiently packs the essential details about ordering and exclusion behavior.

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 reorder tool, the description adequately covers the main behavior and edge cases (unlisted pages). It lacks prerequisites or error conditions, but no output schema exists, and the tool is not complex enough to require more.

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?

The description adds significant meaning to orderedNames by explaining comma-separated format, left-to-right order, and fresh ordinals. However, reportSessionId is not explained in either the schema or the description, leaving a gap for that 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?

The description clearly states the tool's purpose: 'Reorder the report's pages' – a specific verb and resource. It also explains the ordering semantics (left-to-right order, fresh ordinals) and distinguishes from sibling tools like rename_page, add_page, or delete_page.

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 implies use for reordering pages and provides context on how unlisted pages are handled. However, it does not explicitly mention when to use this instead of alternatives (e.g., set_page_tab_order) or when not to use it.

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