get_page_tree

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states what the tool does ('Get the full page tree hierarchy') without mentioning whether it is read-only, what the return structure looks like, or any side effects. For a potential read operation, the description should at least imply non-mutating behavior.

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, short sentence that is front-loaded with the key information. It is concise and contains no unnecessary words, making it easy for an agent to parse quickly.

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 nature of the tool (no parameters, no output schema, no annotations), the description is mostly complete. It specifies the resource and the fact that it returns the full hierarchy, which is the core information needed. However, it could be slightly more explicit about the return format or that it is a read-only operation, but this is not a major gap for a zero-parameter getter.

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 tool has zero parameters, so the input schema is empty. With 0 params, the baseline is 4, and there is nothing for the description to explain beyond what the schema already shows. The description adds no parameter information because none is needed.

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 'Get the full page tree hierarchy' clearly states the action (Get) and the resource (page tree hierarchy). It distinguishes itself from sibling tools like list_pages (flat list) or get_page (single page) by explicitly stating it returns the full hierarchical tree.

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 the tool should be used when a complete page tree is needed, but it does not explicitly state when to use it over alternatives or provide any exclusions. Since it is a simple getter, the implied usage is sufficient, but no explicit guidance is given.

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