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

readOnlyHint=true already signals a safe read, so the bar is lower, and the description adds genuine interpretive context: it explains what usedBy means (the views actually rendering it) and the orphan inference when it is absent. It stops short of describing pagination or ordering behavior, but the added semantic depth is real.

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 key point — the archive bundles returned and their fields — is front-loaded in the first clause, followed by a useful clarification about usedBy. The phrasing is dense and the opening sentence is long, but no sentence is wasted.

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?

Because an output schema exists, the description need not enumerate return values, and it appropriately focuses on field semantics (usedBy, orphan meaning) and a fallback route. It is nearly complete for a zero-parameter list tool, falling just short of stating when to prefer it over sibling list tools.

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 the baseline is 4. With no inputs to document, there is nothing the description needs to compensate for.

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 conveys that this returns archive-page bundles the user authored, along with their fields (path, label, description, usedBy). However, the verb 'list' is only implied via the title rather than stated, and it does not explicitly contrast itself with close siblings like list-archives or list-archive-records. Purpose is clear but sibling differentiation is weak.

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 provides one indirect routing cue — 'If nothing fits, save-archive-page' — and explains an orphan-detection signal via the absence of usedBy. There is no explicit statement of when to reach for this versus the other list/get archive tools, leaving usage largely inferred.

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