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

readOnlyHint=true already declares the safe-read profile, and the description adds real behavioral context beyond it: the context string formats, that term views 'resolve most-specific-first', and that templateId is the binding at that level. It does not discuss ordering, pagination, or emptiness of the result, but the added semantics are substantive.

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?

Everything is packed into a single dense paragraph with inline quoted enums and arrow symbols, which makes it harder to scan than a short front-loaded statement plus a separate workflow note. The information is relevant, but the structure is cramped and the arrow chain is cryptic on first read.

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 an output schema present and no input parameters, the description only needs to frame what the tool is for and how it fits the workflow, which it does. The resolution-ordering note and the downstream chain cover the main ambiguities an agent would face.

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 schema baseline is 4. The description's enumeration of context value shapes applies to returned data rather than inputs, so it adds nothing to parameter semantics, but there is no gap 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 identifies the resource precisely — the archive view contexts a template can be bound to — and enumerates the returned fields (context, label, url, templateId). It never states the verb 'list' explicitly, relying on the name and title, but the resource and scope are unambiguous and distinguishable from siblings like list-archive-pages and list-archive-records.

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 workflow position: 'Pick a context here → save-archive-page → contentSource rule → assign-template-archive', which tells the agent this is the entry point before save-archive-page. There is no explicit when-not guidance or named alternative, but the ordering context is clear.

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