nass_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 it does disclose the pagination behavior and the existence of a next_segment return field, which is genuinely useful since there is no output schema. It does not mention the required job_id, whether the job must be finished, permissions, or error 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?

A single tight sentence with the core action front-loaded and zero filler. The second clause is slightly confusing because next_segment is a response field, not a parameter, but it is still economical.

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 four-parameter tool with a required job_id, no annotations, no output schema, and 0% parameter coverage, this description is too thin. The pagination hint helps, but nothing tells the agent how to form a valid first call or what the returned pages contain.

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 0% and none of the four parameters are explained. 'Pages' loosely gestures at start_segment/count, but job_id (required), with_timestamps, and the default values are left entirely to the schema titles, which convey nothing.

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 (Read) and resource (transcripts) and adds the scope qualifier 'long' plus the pagination mechanic. It is distinguishable from the sibling nass_search_transcript, though it never names or contrasts with that sibling.

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 by 'Read long transcripts' - there is no explicit when-to-use, no when-not-to-use, and no reference to alternatives like nass_search_transcript or nass_export. An agent must guess whether this is for full retrieval versus search.

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