get_session_timeline

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

Discloses behavioral traits like chronological order, prefix match support, pagination, tail, filtering, summary mode, and max_chars control. No annotations exist, so description carries full burden. Lacks explicit statement of read-only nature or performance implications, but overall good.

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?

Three sentences, no fluff. First sentence states purpose, second gives parameter tips, third sets boundaries. Front-loaded and structured for quick reading.

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?

Given high complexity (8 params), no output schema, no annotations, the description covers main use cases, parameter purposes, and exclusion criteria. It provides sufficient context for an agent to use the tool correctly without additional information.

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: explains practical use of 'tail' (checking session end), 'offset' (pagination), 'summary_only' (scanning long sessions), and 'max_chars' (output control). Also mentions 'session id prefix match' not in schema. Schema coverage 75%, but description compensates fully.

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?

Clearly states 'Get a chronological timeline of events in a session.' and distinguishes from sibling tool 'search_in_context' by explicitly saying 'NOT for searching.'

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?

Provides explicit guidance on when to use parameters ('tail' for last N events, 'offset' for pagination) and when not to use (searching vs. paginating in a loop), with a direct alternative tool reference.

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