inspect_session

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

No annotations are provided, so the description carries the full burden. "Read" implies a non-mutating operation and "ordered" conveys result sequencing, but nothing is said about permissions, truncation, how much history is returned, or what happens when a session_id doesn't exist.

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?

Two short sentences with zero filler, and the core purpose is front-loaded ahead of the default-value note. It is tight, though it spends one of its two sentences on a detail the schema already encodes as a default.

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?

An output schema exists, so return-value detail is not required, but the tool has a required `harness` parameter that is undocumented in both description and schema, and with no annotations the safety/behavior profile is unstated. For a three-parameter read tool this is insufficient.

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 0%, yet the description only clarifies session_id (defaults to the newest session). The required `harness` parameter is never explained anywhere, and max_turns/default 10 is left entirely to the schema, so a critical gap remains.

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 ("Read") and a well-defined resource (a session's ordered conversation and tool events), which is enough to separate it from list_recent_sessions and search_sessions_history. It stops short of explicitly naming how it differs from those siblings, so it is clear but not fully differentiated.

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?

There is no guidance on when to inspect a session versus listing recent sessions or searching history; the agent must infer that from the verb "Read." No prerequisites, exclusions, or alternative tools are mentioned.

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