assemblyai_get_paragraphs

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

No annotations are provided, so the description carries full burden. It only states the function without disclosing authentication needs (api_key parameter implies this but not stated), error states (e.g., if transcript not completed), or any side effects. Minimal behavioral transparency.

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 a single, efficient sentence with no wasted words. However, it is almost too brief; a bit more detail could improve without harming conciseness.

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?

Given no output schema and no annotations, the description inadequately covers the tool's behavior. It doesn't describe the return format (list of paragraphs?), prerequisites (transcript must be completed), or error handling. Incomplete for a 2-parameter tool without structured support.

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 baseline is 3. The description adds no additional meaning beyond the schema: it does not explain that api_key is a authentication token or what transcript_id represents (though this is clear from context). No extra value.

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 tool retrieves paragraphs from a completed transcript. It uses a specific verb 'Get' and resource 'completed transcript split into paragraphs', distinguishing it from sibling tools like assemblyai_get_sentences (sentences) and assemblyai_get_transcript (full transcript).

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 usage when paragraphs are needed but does not explicitly state when to use this tool over alternatives like assemblyai_get_sentences. No prerequisites are mentioned, such as the transcript being in 'completed' status, which is critical for correct invocation.

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