move_confluence_page

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

With no annotations provided, the description must fully disclose behavioral traits. It only states the intended outcome ('move under a new parent') without covering important details such as side effects (e.g., impact on child pages), required permissions, or whether the operation is reversible. This is insufficient for a mutation tool.

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 a single sentence that directly conveys the tool's purpose and required inputs. It is front-loaded with the key action and resource, with no extraneous information.

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 (two string parameters) and the presence of an output schema, the description provides adequate high-level context. However, it lacks detail on preconditions (e.g., user permissions, page existence), error scenarios, and the effect on the page hierarchy, which would be helpful for an agent to use the tool correctly.

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 input schema has no descriptions for its two parameters (0% schema_description_coverage). The description adds basic semantic meaning by identifying 'page_id' as the page to move and 'target_parent_id' as the new parent. However, it does not elaborate on how to obtain these IDs, any constraints (e.g., page must exist), or format expectations, leaving some ambiguity.

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 explicitly states the action ('move') and the resource ('Confluence page'), and specifies the required inputs. It clearly distinguishes from sibling tools like 'get_confluence_page', 'create_confluence_page', and 'update_confluence_page' which serve different purposes.

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 indicates the tool is for moving a page under a new parent, which implies usage context. However, it does not provide explicit guidance on when to use this tool versus alternatives (e.g., updating page properties), nor does it mention any prerequisites or exclusions.

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