reorder_sheet_pages

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

Annotations indicate destructiveHint=true, suggesting reordering may cause irreversible changes, but the description does not disclose any behavioral traits beyond the basic operation. It fails to explain implications like broken references or required permissions.

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 short and to the point, using a structured Args list. Every sentence contributes, though it could be slightly more informative without becoming verbose.

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?

Despite having an output schema (not visible), the description does not mention return values or error conditions. It also omits important details like what happens if invalid UUIDs are provided or if the sheet list is incomplete. The tool's destructive nature should be addressed.

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 brief meaning to both parameters: 'page_order' is a list of sheet UUIDs in desired order, and 'schematic_path' is the file path. Since schema description coverage is 0%, this partial explanation provides some value, but it lacks details like default value behavior for schematic_path or format constraints on UUIDs.

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 reorders hierarchical sheets by specifying a UUID order. It uses a specific verb ('Reorder') and resource ('hierarchical sheets'), and the name reinforces this. However, it does not explicitly distinguish itself from the sibling 'move_hierarchical_sheet' tool.

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 provides no guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or scenarios where it should not be used. It simply states the function with no usage context.

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