assemblyai_get_transcript

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

No annotations are provided, so the description carries the full burden. It states 'Get the status and results,' indicating a read-only operation. However, it does not disclose any behavioral traits such as potential polling, rate limits, or what happens if the job is not yet complete. The description is minimal and lacks depth for a non-annotated tool.

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 sentence that is clear, direct, and front-loaded. Every word is necessary and there is no redundancy or 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?

The tool has 2 required parameters and no output schema. The description does not explain what the response looks like (e.g., fields like status, text, confidence). While the schema covers parameters, the lack of output schema means the agent may not know what to expect. The description is adequate for a simple retrieval but could be more complete.

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% with both parameters (api_key, transcript_id) having descriptions in the schema. The description adds no additional meaning beyond what the schema already provides. With high schema coverage, the baseline score is 3.

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's purpose: 'Get the status and results of an AssemblyAI transcription job.' It uses a specific verb ('Get') and resource ('status and results of a transcription job'), distinguishing it from sibling tools like assemblyai_transcribe (which creates a job) and assemblyai_list_transcripts (which lists all jobs).

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 after creating a transcription job via assemblyai_transcribe, as it requires a transcript_id. However, it does not explicitly state when to use this tool versus alternatives, nor does it provide exclusions or preconditions. The context is implied but not spelled out.

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