get_session

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

Annotations already establish readOnly=true, idempotent=true, non-destructive=false, so the safety profile is covered. The description adds substantive value by detailing what each view returns (args/ok/summary/duration for journal, per-tool counts and durations for metrics), which is meaningful behavioral context 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?

One front-loaded sentence with the resource and view breakdown, no filler. It is dense and readable, though the parenthetical enumeration is heavy enough that a slightly more structured form might scan faster.

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 no output schema, the description carries the burden of explaining return values, and it does so for all three views. Remaining gaps (pagination/ordering beyond 'most recent N', session default behavior) are minor for a read-only introspection tool.

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 coverage is 100%, so the enum values and limit semantics are already documented. The description nonetheless enriches the view parameter by explaining the distinct content of each mode and notes that limit applies specifically to journal, adding meaning the bare schema descriptions do not convey.

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?

States a specific verb (returns) and resource (this session's record) and immediately enumerates the three views with what each yields. An agent can distinguish it from list_sessions (which enumerates sessions rather than reading one session's contents) without opening either schema.

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 view names imply which one to pick for a given goal, but the description never states when to use get_session versus alternatives like session_diagnostics, list_sessions, or export_debug_report, nor when a view is preferable. Usage is left to inference.

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