Deliberation

session-annotate

Append a freeform note to a persisted session's audit trail locally, avoiding provider calls.

Instructions

Append a freeform note to a persisted session's audit trail - an additive local write, no provider calls. Requires sessions.persist. Returns a text-wrapped JSON envelope { session } (the updated record), or { error } when persistence is off or the id is unknown.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sessionId": "<sessionId>",
      "note": "<note>"
    },
    "name": "session-annotate"
  }
}

Input Schema

Name	Required	Description	Default
`note`	Yes	Freeform text appended to the record's audit trail.
`sessionId`	Yes	Id of the persisted session record to annotate.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv3.8.1Jun 18, 2026
- addedInput schema / properties / note / description
```
Added value: +"Freeform text appended to the record's audit trail."
```
- addedInput schema / properties / sessionId / description
```
Added value: +"Id of the persisted session record to annotate."
```
First observedv0.1.0Jun 17, 2026

TDQS

A4.5/5.0

Behavior5/5

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

The description details the additive, non-destructive nature of the operation and states that it is a local write with no provider calls. This adds valuable context beyond the annotations (which already indicate non-read-only and non-destructive). It also explains error conditions and return format.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise: two sentences that efficiently convey purpose, prerequisites, and return behavior. Every sentence serves a distinct purpose with no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simplicity of the tool (two required params, no output schema), the description provides complete information: it explains the action, prerequisites, side effects (additive local write), error conditions, and return format. No additional context is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and both parameters have clear descriptions. The description does not add additional parameter-level detail beyond what the schema provides. As per guidelines, with high schema coverage the baseline is 3, and the description does not increase it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Append'), the resource ('persisted session's audit trail'), and key characteristics ('additive local write, no provider calls'). It distinguishes from sibling tools, which are about analysis, consultation, or retrieval, not annotation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly mentions the prerequisite 'Requires sessions.persist', which provides a clear condition for when to use this tool. It also notes that an error occurs when persistence is off. However, it does not provide explicit alternatives or when-not-to-use scenarios, which would elevate the score to 5.

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