reorder_sheet_pages

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

The description does not add behavioral context beyond what annotations already provide. Annotations mark destructiveHint=true, and the description merely repeats the mutating nature with 'Reorder'. There is no disclosure about file modification, irreversibility, or side effects, so the value added is minimal.

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 extremely concise, with a one-sentence purpose statement and a short args list. No filler words or redundant information. Information is front-loaded and easy to scan.

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 relatively simple tool with an output schema and clear annotations, the description covers purpose and parameters adequately. It could be more complete by noting prerequisites (e.g., UUIDs must refer to existing sheets) or error behavior, but these are not critical given the schema and context.

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?

With 0% schema description coverage, the description fully compensates by explaining 'page_order' as a list of sheet UUIDs and 'schematic_path' as an optional path to the root .kicad_sch file, including the default behavior. This provides essential meaning beyond the raw schema.

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 action ('Reorder'), the target resource ('hierarchical sheets'), and the method ('by specifying the desired UUID order'). It distinguishes itself from sibling tools like move_hierarchical_sheet or duplicate_sheet by focusing on global page ordering.

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 purpose inherently conveys when to use it: when the user wants to change the order of schematic pages. It does not explicitly mention alternatives or exclusions, but the context is clear enough for an agent to select this tool over siblings that move individual sheets.

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