Browse the page tree

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds valuable behavioral details beyond that: mode semantics for filtering folders/pages and the important caveat that wide levels are truncated to the result budget. This enriches the agent's understanding without contradicting annotations.

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?

Three sentences, each earning its place: the core action and differentiation, the mode values, and the truncation caveat. The most important information is front-loaded, and there is no redundant wording.

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 read-only listing tool with no output schema, the description covers the key behavioral distinctions and result-budget truncation. It does not describe output fields or error behavior, but the schema and annotations provide enough support for correct invocation.

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 75%, and the description compensates for the one undocumented parameter (mode) by explaining exactly what ALL, FOLDERS, and PAGES return. It does not add detail for path, locale, or include_ancestors, but those already have schema descriptions.

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 states a specific verb and resource: 'Lists the pages and folders directly under a path.' It also differentiates the tool from search by calling it 'the structural view a wiki has and a search does not,' making its role clear among siblings like search_pages and grep_pages.

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 gives clear context for when the tool is appropriate—when a hierarchical, structural view is needed rather than a search result. It does not explicitly name alternative sibling tools or state when not to use them, so it falls slightly short of full exclusions.

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