wikijs_get_page_tree

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

With no annotations provided, the description carries the full burden of disclosure. It mentions returning folders/pages with depth info but does not state that the operation is read-only, nor does it address any performance implications or authentication needs. The lack of behavioral context is a gap.

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 consists of two concise sentences, front-loading the purpose and key output details. No superfluous information is present.

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 lack of output schema and the complexity of representing a tree structure, the description is somewhat complete but fails to specify the exact shape of the output or how depth info is represented. Additionally, it does not differentiate from wikijs_get_navigation, which may also provide hierarchical information.

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 covers all 5 parameters with clear descriptions, achieving 100% schema coverage. The description adds value by noting the output includes depth info, which is not in the schema. This complements the parameter definitions.

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 tool retrieves the page tree hierarchy for site navigation and structure discovery. It mentions returning folders and/or pages with depth info, which distinguishes it from sibling tools like get_page_by_id or list_pages that 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 implies use for navigation and structure discovery but does not explicitly guide when to use this tool versus related siblings like wikijs_get_navigation or wikijs_list_pages. No exclusions or alternatives are mentioned.

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