Read a Jot

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), and the description adds genuine conditional behavior: the text timeline is only returned 'when a session was recorded.' That discloses a variability in the response an agent otherwise could not predict, which is real value beyond the annotations.

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?

A single front-loaded sentence opens with the core purpose, and the em-dash aside adds the response contents plus the agent-relevant reason for the timeline. Efficient overall, though the mid-sentence aside slightly complicates parsing.

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?

With no output schema, the description correctly shoulders the job of describing return contents (repro context, thread, conditional timeline), and annotations cover the read-only safety profile. For a one-param read tool it is close to complete, missing only the commentId format.

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 description coverage is 0% and the single commentId parameter is undocumented in the schema, so the description carries the burden -- but it only implies the ID identifies 'one comment' and gives no format or sourcing guidance. With one self-naming parameter, this is minimally adequate rather than compensating for the gap.

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 action and resource: retrieving full detail for one comment, enumerating what that detail includes (repro context, thread, timeline). It is clear about scope (single comment) but never distinguishes itself from siblings like fetch_feedback, so it lands at 4 rather than 5.

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?

Usage is only implied: you call it to get detail on one comment, and the closing rationale hints at the value of a text timeline over an unwatchable replay. No explicit when-to-use condition, no exclusion, and no routing to alternatives such as fetch_feedback is provided.

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