move_collective_page

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

Annotations declare the safety profile (not read-only, not idempotent, non-destructive), and the description meaningfully extends it: 'Every call makes another copy' explains the non-idempotent semantics, the landing position ('first among its new siblings') is disclosed, and permission requirements are stated. This is real context beyond the structured fields.

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?

Front-loaded summary sentence, then compact Args and Returns sections. Every line adds a distinct constraint or parameter meaning with no filler.

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 5-param mutation tool, the description covers purpose, permissions, edge cases (self/subpage), parameter meaning including defaults, and the return shape. An output schema exists and the description correctly defers detail to it while noting the copy-vs-move return difference.

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 coverage is 0%, so the description must carry the parameters, and it does: each of the five params is explained, including defaults for to_collective_id (0 = stay in this one) and the special parent_id value 0 for top level. No gap remains.

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?

States a specific verb pair (move or copy) plus the resource (page with its subpages) and the target scope (under another page, in this or another collective). This clearly distinguishes it from siblings like update_collective_page, trash_collective_page, and delete_collective_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?

Provides concrete when/when-not constraints: needs edit rights in both collectives, and a page cannot go under itself or its own subpages. It does not name alternative sibling tools to redirect to, so it stays short of the full 5.

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