flightlog_get_session

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

Since no annotations are provided, description carries full burden. It states 'Retrieve' (implying read-only) and describes what the transcript includes: user questions, answers, tool calls, decisions. No destructive behavior indicated, no contradictions.

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 sentences, no wasted words. First sentence states purpose, second provides usage context and details. Front-loaded and efficient.

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?

No output schema exists. Description provides a high-level summary of return content (user asked, answers, tool calls, decisions) but does not specify format or structure. Adequate for typical use.

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 coverage is 100%, so baseline is 3. Description does not add extra semantic meaning beyond what the schema already provides for the two parameters. It mentions source for session_id and default for include_tool_io, but schema already covers that.

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?

Description clearly states 'Retrieve the full transcript of a past Claude Code conversation', with a specific verb and resource. It distinguishes from siblings by mentioning 'Use after flightlog_search'.

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 says 'Use after flightlog_search to read the complete context of a session', providing clear context. Does not mention when not to use, but the guidance is sufficient.

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