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

Adds substantial context beyond the annotations: the transcript may contain personal data and secrets with explicit handling guidance, another agent's session reads as not found, and a Valet account must be connected. Annotations already cover the read-only/idempotent safety profile, and the description layers on privacy and access behavior.

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?

Front-loaded with the resource and returned fields, then the events switch, the privacy caveat, and the access note. Dense and mostly waste-free, though the privacy sentence is comparatively long.

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 5-param read tool with no output schema, the description compensates by enumerating return fields and covering auth, cross-agent scope, and the transcript/limit interaction. Nothing an agent needs to call it correctly is missing.

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 the baseline is 3, but the description adds ordering semantics the schema omits: events returns the session's FIRST events up to limit (default 50, max 200), clarifying truncation direction.

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?

States a specific verb and resource ("Read one of an agent's conversation sessions") and enumerates the returned fields (status, title, channel, message count, timestamps). It clearly separates a single-session read from the list-style siblings, though it never names a sibling tool explicitly.

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?

Gives a clear conditional: pass events:true for the transcript, omit for details alone, with limit bounds. It also states the auth prerequisite and the cross-agent behavior, but does not explicitly contrast with list_sessions or other get_* tools.

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