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

With no annotations, the description carries the full burden. It does disclose the pagination contract ('page=1..N until done=true'), which is genuinely useful behavioral information since no output schema exists to reveal the done flag. It does not state that the operation is a read with no side effects, nor anything about payload size or ordering, leaving gaps for a zero-annotation tool.

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?

A single dense sentence, front-loaded with the trigger condition and followed by the payload and the loop rule. Nothing is wasted, though the telegraphic phrasing ('full constitution + memory + last session') reads like shorthand rather than a complete sentence, which slightly raises parsing effort.

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?

For a one-parameter bootstrap tool with no output schema, this covers the essential contract: what triggers it, what it returns at a high level, and how to iterate to completion. The absence of an output schema means the 'done' flag and payload shape are undocumented elsewhere, and the description only partially fills that gap, but the critical calling guidance is present.

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 0% for the single 'page' parameter, so the description must compensate, and it does: 'page=1..N until done=true' explains both the iteration range and the termination condition. This is meaningfully more than the bare integer schema provides. It stops short of saying whether page numbering is 1-based by default (schema shows default 1) or what happens past the last page.

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 names the payload ('full constitution + memory + last session') and its trigger point, which lets an agent infer this is a bundled bootstrap fetch rather than a single-resource get. However, no verb is stated (retrieve? load? assemble?), so the action itself is left implicit. It is distinguishable from siblings like constitution_get and memory_search only by inference from the union of resources.

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?

Timing is explicit and unambiguous: 'after install, and at every session start when installed.' That answers the when-to-use question decisively. It does not name alternatives for cases where the agent only needs the constitution or only memory (constitution_get, memory_search), which keeps it from a 5.

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