PatchWarden

audit_session

Run 16 deterministic checks to independently verify a finalized session's changes and receive a pass, warn, or fail decision.

Instructions

Independently audit a Direct session's changes. Performs 16 deterministic checks and returns pass/warn/fail decision. Requires session to be finalized first.

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": {
      "session_id": "<session_id>"
    },
    "name": "audit_session"
  }
}

Input Schema

Name	Required	Description	Default
`session_id`	Yes	Session ID to audit

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.5.0Jul 8, 2026

TDQS

A4.4/5.0

Behavior4/5

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

The description adds behavioral context beyond annotations: 'Performs 16 deterministic checks' and 'returns pass/warn/fail decision.' While readOnlyHint is false, the description does not claim read-only behavior, so there is no contradiction. It could further clarify side effects, but for an audit tool the added detail is useful.

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 two sentences, front-loaded with the verb and resource, and contains no filler. Every sentence earns its place: the first states what it does, the second explains behavior and prerequisite.

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

Completeness4/5

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

For a tool with a single parameter and no output schema, the description sufficiently covers purpose, behavior, and prerequisite. It lacks details about the 16 checks or what pass/warn/fail mean, but these are not critical given the simplicity of the tool and existing annotations.

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

Parameters4/5

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

The schema already fully describes the single parameter 'session_id' with 100% coverage. The description adds contextual meaning by stating the session must be finalized first, which is valuable beyond the schema and helps the agent understand valid input.

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 tool's purpose: 'Independently audit a Direct session's changes' with a specific verb ('audit') and resource ('session's changes'). It also distinguishes itself from siblings like 'audit_task' and 'safe_audit_direct_session' by focusing on Direct sessions and providing a pass/warn/fail decision.

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 provides a clear prerequisite: 'Requires session to be finalized first.' This gives context on when to use the tool, but it does not explicitly mention when not to use it or alternative tools, so it stops short of a 5.

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

Deploy Server