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

With only readOnlyHint provided, the description carries useful extra behavioral weight: it explains what ours=false means (theme files are rule-able but not readable/editable/deletable here) and that usedBy identifies the views actually pointing at an item, so an empty usedBy signals an orphan. That is genuine operational context beyond the annotation, though it stops short of describing ordering or result size.

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 is compact but structured as a dense, run-on field glossary rather than a front-loaded statement of purpose. The single most important sentence — what this tool does — is missing, so the reader must reconstruct it from the field list.

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?

Complexity is low (read-only, no params) and an output schema exists, so the exhaustive enumeration of return fields is largely redundant. The description instead leaves the core gaps — a clear action statement and when-to-use routing versus get-single-page — partially open, making it only adequately complete.

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 takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a no-argument tool applies. The field glossary instead duplicates the output schema, which does not help parameter selection.

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 opens with a topic fragment ("What a template's content slot can render") and never states the action verb of listing single pages. The resource domain is gestured at via "path", "contentSource rules[].file" and "usedBy — the views actually rendering it", so an agent can infer it enumerates renderable single pages, but it is not clearly distinguished from siblings like get-single-page, list-template-pages, or save-single-page.

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?

There is one latent routing hint ("If nothing fits, save-single-page") plus an implicit constraint that ours=false items are "not readable, editable or deletable here", which nudges the agent toward other tools for those items. However, there is no explicit statement of when to call this list versus get-single-page, nor any prerequisite or filtering guidance.

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