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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing the response shape field-by-field (necessary since there is no output schema) and by revealing that pageId switches the tool from a list into a single-page settings read — a behavioral nuance the annotations do not capture.

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?

Two dense sentences, front-loaded with the list behavior and its return fields, then the alternate mode. No filler or restatement of the title.

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?

With no output schema, the description correctly carries the return-value burden by naming the fields returned in each mode. A minor gap remains: it does not state that both parameters are optional or what happens when id is omitted (default/selected site), which matters for a zero-required-parameter tool whose scope otherwise depends on ambient state.

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%, so the baseline is 3. The description exceeds the baseline: it tells the agent that pageId is not a filter but a mode switch that changes the returned payload from page summaries to access policy/theme override details, which the schema's terse 'Show one page's settings' does not make clear. The id parameter's scoping is implied only through 'the site's pages'.

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?

States a specific verb and resource ('List the site's pages') and enumerates the returned fields (id, name, url, file, home/404 flags), plus the second mode where pageId yields access policy, body class and theme overrides. It does not explicitly differentiate from close siblings like outline_page or update_page, so it is clear but not sibling-routing.

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?

'Use it to get page ids' gives an explicit invocation context for the no-argument case, which is the primary workflow (list, then act on an id). The pageId mode is described by its output rather than by when to prefer it over update_page or outline_page, and no exclusions are stated.

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