Get Session Brief

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

With no annotations provided, the description carries the full behavioral disclosure burden. It explicitly declares the operation is read-only and clarifies that it does not open a session or mark one as started. It also lists the output categories. It does not cover authorization or edge-case behavior, but for a simple read tool these omissions are minor.

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?

The description is two sentences with no filler. It front-loads the most important fact ('Read-only'), then gives a concrete content list, and closes with a useful sibling distinction. Every clause earns its place.

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?

Given the tool's simplicity (one optional parameter, no output schema, no annotations), the description is complete enough for an agent to invoke it correctly. It explains the safety profile, what the brief contains, and how it differs from start_session. Nothing essential for selection or calling is missing.

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 100%, and the only parameter, 'project', is already documented in the schema as 'Project name or ID'. The description does not add extra parameter-level meaning, so the baseline score of 3 applies.

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 clearly states what the tool does: it returns a read-only summary of what changed since the last session ended, and enumerates the exact content categories (commits, branch/working-tree state, task changes, blockers, decisions, notes). It also distinguishes itself from start_session, leaving no ambiguity about scope.

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?

The description gives explicit when-to-use context ('what changed since the last session ended') and an explicit alternative/exclusion: 'Unlike start_session, this does not open a session or mark one as started.' This tells the agent both when to pick this tool and why it is not a session-opening action.

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