get_transcript

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

With no annotations, the description carries the full burden and does well: it discloses that mid-recording reads are safe because the file is line-buffered, and that tail_lines takes precedence over since_offset. It does not mention auth/permission requirements or whether reads can block, so it is strong but not exhaustive.

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-loads the purpose and the safety/polling guidance, then uses compact Args/Returns blocks. Every sentence — including the precedence rule and return field list — carries information an agent needs, with no filler.

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 3-param read tool with no annotations and no output schema, this covers the essentials: purpose, mid-recording safety, all parameter defaults and interactions, and the return object shape ({session_id, text, end_offset, line_count, is_recording, last_modified}). Nothing needed 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 description coverage is 0%, so the description must compensate entirely, and it does: session_id (defaults to active, else most recent), tail_lines (last N lines), and since_offset (bytes after offset, with precedence rules) are all explained with behavior the schema cannot convey.

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+resource: 'Read the transcript for the active (or named) session.' The resource (transcript) is clearly distinct from the siblings get_status/list_sessions/start_recording/stop_recording, but the description never names or contrasts those siblings explicitly, which is what a 5 requires.

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 clear operating context: 'Safe to call mid-recording' and a concrete polling pattern ('pass back the end_offset from the prior call'). It stops short of saying when NOT to use it or pointing to an alternative sibling, so it is not a 5.

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