get_session_transcript

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

No annotations are provided, so the description carries the full burden. "Retrieve" implies a read, but nothing is said about permissions, transcript size or truncation, pagination, time bounds, or whether archived sessions are covered — all relevant for a potentially large log dump.

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 sentence, front-loaded with the verb and scoped at the end; every clause (logs, tool invocations, inbox events) carries distinct information about what is returned.

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?

For a simple one-parameter read tool with no output schema, the enumeration of contents partially substitutes for a return-value description. However, nothing addresses volume, truncation, or ordering of the transcript, which are the main unknowns an agent would face.

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?

There is a single required parameter with 100% schema description coverage ("ID of the session to inspect"), so the schema already does the work. The description adds only the framing that the ID selects which session's logs to fetch, no format or sourcing detail.

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 ("Retrieve") and enumerates the resource contents: conversation logs, tool invocations, and inbox events, scoped to "a specific session." This clearly separates it from siblings like list_sessions or check_inbox, though it never names an alternative explicitly.

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?

Usage is only implied by "for a specific session" — an agent can infer this is a per-session deep-inspection tool, but there is no explicit when-to-use, when-not-to-use, or routing to siblings such as check_inbox or get_task_status.

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