get_session_journal

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

Description declares read-only behavior and specifies return JSON structure with fields: calls, filesRead, zeroResults, duplicates. Annotations already indicate readOnlyHint and idempotentHint, but description adds concrete output details beyond 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?

Description is extremely concise with a single sentence and a brief JSON sample. All information is front-loaded and every word adds value.

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 zero parameters and no output schema, the description fully covers what the tool does, its return structure, and usage context. No gaps identified.

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?

No parameters in input schema, so description doesn't need to explain parameters. Baseline score of 4 applies as per guidelines for zero-parameter tools.

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 the tool returns session history including tool calls, files read, zero-result searches, and duplicate queries. It distinguishes itself from sibling get_session_snapshot by mentioning 'for a compact snapshot' alternative.

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?

Explicitly advises 'Use to avoid repeating work' and provides alternative: 'For a compact snapshot use get_session_snapshot instead.' Clear guidance on when to use and when not.

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