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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered and "Reads only" is largely redundant. The description does add real value beyond the annotations by disclosing the shape of the result (page address, file, variable/`:slug` parts, folder names, page counts, collections, and how Xodia can change pages) and by clarifying that folders may be implicit rather than stored objects.

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?

It front-loads the verb and resource, then packs the return-value detail into a single structured sentence, followed by two short actionable sentences. The enumeration is dense but every clause carries information; nothing is obviously filler.

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?

There is no output schema, so the description carries the burden of explaining return values, and it does so thoroughly for both pages and folders. Combined with the read-only annotations and fully documented parameters, an agent has enough to call it correctly; only explicit sibling routing is missing.

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 coverage is 100% and both parameters are documented in the schema, including the branch default and where projectId comes from. The phrase "on a branch" hints at the branch parameter's role but adds no syntax or format detail beyond the schema, so the baseline of 3 applies.

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 site's pages and folders on a branch") and then enumerates what each entry contains, so an agent knows exactly what comes back. It does not explicitly name the sibling list tools it differs from (list_collections, list_files), so it falls short of full sibling differentiation.

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?

It gives a concrete prerequisite: "Read it before adding or moving pages," which ties it to create_page and move_page. It offers no explicit when-not-to-use case or named alternative, so the guidance is clear but not exhaustive.

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