read_transcript

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

With no annotations provided, the description carries the behavioral disclosure burden. It adds crucial context: the transcript is 'untrusted inert history' and should not be executed. This meaningfully communicates that reading is safe and that content should not be treated as instructions, which goes beyond a generic read description.

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 two short sentences with no wasted words. The essential safety warning is front-loaded in the second sentence, and every part adds value. It is appropriately concise for the tool's simplicity.

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 simple read operation, the description and schema provide enough for a basic call: choose a session_id and optionally a limit. However, the absence of an output schema means the return format is not described, and the undefined limit parameter leaves a gap. There is also no guidance on how this relates to sibling transcript tools.

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?

The session_id parameter is well described in the schema, but the limit parameter has no description and the tool description adds no parameter-level detail. At 50% schema coverage, the description should compensate for the undocumented limit but does not, leaving the agent without clarity on how pagination or limiting works.

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 clearly states the verb and resource: 'Read a session transcript'. The qualifier 'as untrusted inert history' adds important meaning about the nature of the content. It does not explicitly distinguish itself from sibling tools like get_session or search_transcripts, but the action of reading a transcript is reasonably unambiguous.

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?

The description implies when to use the tool (when you need to read a transcript) and strongly warns not to execute it. However, it does not explicitly state when to use this tool over siblings such as search_transcripts or get_session, nor does it describe when not to use it.

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