session

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

Discloses read-only nature, chronological order, and paging behavior. Without annotations, it adequately covers behavioral traits but could be more explicit about error handling or return format. Still strong.

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?

Four sentences front-loaded with main purpose, no fluff. Every sentence adds value: purpose, usage context, paging, read-only nature.

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?

Complete for a simple read tool with no output schema. Covers all needed aspects: what it does, when to use, how to page, safety (read-only). No missing context.

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?

Adds meaning beyond schema by explaining the purpose of session_id (from list_sessions/search) and the roles of limit/offset for paging. Schema already covers descriptions, but description enhances context.

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 it reads a full conversation in chronological order, specifying the verb (read), resource (conversation/session), and ordering. It distinguishes from siblings by mentioning using session_id from list_sessions or search and contrasting with searching across many.

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 tells when to use: after having a session_id from list_sessions or search, and wanting to read a whole session in order rather than searching across many. Provides clear context and alternatives.

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