get_session_messages

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

The description simply says 'retrieve', implying a read-only operation, but does not disclose any additional behavioral traits such as auth requirements, rate limits, pagination, or data format. With no annotations provided, the description carries the full burden but adds little beyond the literal action.

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 a single, clear sentence with no redundant words. It is efficient but not overly minimal; however, it omits potentially useful structural details that could make it more informative. Overall, it is appropriately sized for a simple tool.

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 and no annotations, the description does not explain what the transcript contains, how it is structured, or any limits such as maximum message count. While the term 'full conversation transcript' gives a general idea, it lacks the operational detail an agent would need to handle the response effectively.

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?

The schema has one required string parameter, sessionId, with zero description coverage. The tool description mentions 'coding agent session' which indirectly suggests the parameter is a session identifier, but it does not explicitly explain how to obtain it, its format, or any special constraints. This is minimal compensation for the lack of schema documentation.

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 a specific action ('Retrieve the full conversation transcript') and identifies the resource ('coding agent session'). This is distinct from sibling tools like list_projects or get_session_status, which target different entities.

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?

No guidance is given on when to use this tool versus alternatives, such as get_session_status or send_message. There is no mention of prerequisites, context, or exclusionary conditions, leaving the agent to infer usage solely from the tool name and description.

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