pond_get_session

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

Annotations already declare readOnlyHint and idempotentHint, but the description adds substantial behavioral context: chronological ordering, paging semantics, from="end" reading final state, subagent footer listing, and that message_id resolves to parent session. It also warns about late conclusions superseding early ones.

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 dense but every sentence serves a purpose: purpose, id resolution, paging, subagent navigation, and bulk-export exclusion. It is front-loaded with the core purpose and avoids filler.

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 tool with no output schema and nontrivial paging, the description covers the key aspects: content of the transcript, paging methods, id sources, and subagent handling. It points to resource schema://pond for return format, but does not detail response fields. Slight gap, but still robust enough for an agent to select and invoke correctly.

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?

Though schema coverage is 100%, the description significantly enriches parameter meaning: it explains that message_id resolves to parent session, from="end" reads most recent turns first, and describes how after_message_id/before_message_id act as page markers. This goes far beyond the schema's basic field definitions.

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 opens with a specific verb and resource: "Read a whole past session as a chronological transcript." It clearly distinguishes from siblings (pond_get_message, pond_search, pond_sql) by noting tool bodies are one message away and that bulk export should use `pond copy`.

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 frames when to use the tool: "the tool for analyzing, reviewing, or summarizing a session," and gives a clear alternative for bulk export. Also explains how to obtain the id from pond_search or a subagent footer, and advises against bulk export, directing to `pond copy`.

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