Project context

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

Annotations flag destructiveHint=true, readOnlyHint=false and idempotentHint=false, yet the description never says which actions overwrite or destroy state, whether condense/snapshot/archive are reversible, or what permissions are needed. It adds only the dryRun default for condense, which the schema already documents. For a destructive multi-action tool this is a material disclosure gap, though nothing in the text contradicts the annotations.

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 compact paragraph that front-loads the resource and then the action inventory, with conditional rules clustered at the end – appropriate density for a 33-parameter dispatcher. Minor waste in awkward phrasing such as 'history the context documents', which reads as a verb and costs a beat of comprehension, but overall every clause carries information.

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 8 actions, 33 parameters and no output schema, the description leaves the agent unable to predict what any action returns (view digest, history range, search hits, constraint review) or what side effects update/condense/archive produce. Only three of the eight actions get any behavioral constraint, and pagination/size semantics (page, pageSize, sizeOnly, compact) are untouched. The complexity demands substantially more than this.

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 description coverage is 88%, so per-parameter meaning is largely handled by the schema and the baseline would be 3. The description earns above baseline by stating cross-parameter coupling that no single field description captures: query is required specifically for search, source specifically for snapshot, and condense is dry-run unless dryRun=true. It does not, however, clarify the action-parameter interactions for update, history, or the nextStepAction/constraintAction sub-dispatchers.

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 resource ('the record's documents and lists') and enumerates the eight action families (view, update, condense, snapshot, history, next_steps, constraints, search), which lets an agent recognize the tool's scope without opening the schema. It also draws a boundary against rbook_session ('New next steps and constraints come from rbook_session capture'). What keeps it from a 5 is that update/condense/snapshot/history are only restated as verbs, not explained, so the agent learns the names but not what each operation actually accomplishes.

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?

Useful gating rules are given for three actions ('search needs query; snapshot requires source; condense applies unless dryRun=true') and one negative routing hint sends creation of next steps/constraints to rbook_session. However, there is no guidance for the obvious sibling overlaps: why use search here versus rbook_decisions or rbook_learnings, or when to use this tool's next_steps/constraints lists versus the dedicated tools. Usage is implied by the action list rather than explained.

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