wikijs_create_nested_page

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Create' implies mutation, but the description does not state what happens when a parent path does not exist, whether intermediate pages are auto-created, privacy/publish defaults, or any permission requirements. The single detail about hierarchy adds some context but leaves significant behavioral uncertainty.

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, concise sentence with the verb and key differentiator front-loaded. There is no redundant wording, and it is appropriately short for its limited content.

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 has 9 parameters, no output schema, and no annotations, the one-sentence description is not sufficient. It leaves unclear how parentPath behaves, what the resulting URL structure looks like, and how this tool fits into the broader workflow alongside the many sibling creation and management tools.

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%, so all 9 parameters are already documented in the input schema. The description adds no additional parameter-level meaning, so the baseline score of 3 is appropriate.

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 verb ('Create') and resource ('a page'), and the qualifier 'with hierarchical path structure' distinguishes it from the sibling wikijs_create_page, which presumably creates a flat page. However, it does not explicitly name the sibling or fully outline the tool's scope, so it stops short of a 5.

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 hierarchical path language implies this tool is for creating nested pages under a parent path, especially given the required parentPath parameter. But the description does not explicitly contrast it with alternatives like wikijs_create_page or provide when-not-to-use guidance, leaving the usage guidance mostly implicit.

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