pbir_reorder_pagesSet Power BI report page order by passing an array of page IDs in the desired sequence, so report navigation matches the intended layout.
Set the page order
| Name | Required | Description | Default |
|---|---|---|---|
| pageOrder | Yes | Array of page IDs in desired order |
Changes observed during successful MCP inspections.
v0.9.6Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description does not disclose any behavioral traits beyond the basic action. Annotations only include 'openWorldHint: false', which does not add behavioral context. There is no mention of side effects, permissions, or error conditions, leaving the agent underinformed about what happens when reordering pages.
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, using a single sentence to convey the purpose. While it sacrifices detail, it is front-loaded and direct. It could benefit from slightly more context, but for a simple operation, the brevity is acceptable.
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?
Given the tool's simplicity and full schema coverage, the description is minimally adequate. However, it lacks information about return values (none provided), error handling, or prerequisites (e.g., page IDs must exist). For a complete context, the description should at least hint at these aspects.
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 description coverage is 100% for 'pageOrder', and the schema adequately describes it as 'Array of page IDs in desired order'. The description adds no additional meaning beyond the schema. Baseline score of 3 is appropriate as schema does the heavy lifting.
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 'Set the page order' uses a specific verb ('Set') and resource ('page order'), clearly indicating this tool reorders pages. It distinguishes from sibling tools like 'pbir_rename_page' or 'pbir_delete_page' which perform different operations. However, it is very brief and could be more descriptive.
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?
There is no guidance on when or when not to use this tool. No alternatives are mentioned, and no context is provided about prerequisites (e.g., needing existing pages). The description lacks any usage direction beyond stating the action.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.