set_subpage_order

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

The description adds substantial context beyond annotations, including validation rules (duplicates rejected), the effect of an empty array (fallback to Collective sort), and a conditionality note (only for users with 'byOrder' page order). These details are not fully captured by the annotations alone.

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 compact and well-structured, consisting of three sentences that each convey a distinct piece of essential information without redundancy. It is easy to parse and directly relevant to invoking the tool.

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 simple parameter set (three integers/array) and no output schema, the description covers all necessary operational aspects: the action, constraints, and side effects. It provides sufficient context for an agent to use the tool correctly without requiring additional details.

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 clarifies the semantics of subpageOrder by specifying that ids must be direct children and that an empty array resets to default. However, collectiveId is not explicitly explained, despite being required; the schema only provides descriptions for two of three parameters, so the tool description adds value but leaves collectiveId implicit.

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 uses the specific verb 'Set' and precisely identifies the resource as 'explicit left-to-right ordering of a page's immediate child pages'. It clearly differentiates from sibling tools like move_page or update_page by focusing solely on ordering subpages.

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 explicitly states when to use the tool (to set explicit ordering) and provides key behavioral constraints: every id must be a direct child, duplicates are rejected, empty array clears manual order, and the effect is conditional on user's 'byOrder' setting. This gives clear guidance without ambiguity.

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