import_transcript

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

No annotations provided, so description carries the burden. It discloses skipping Whisper and the requirement for word-level timestamps, which are key behaviors. However, it does not mention side effects (e.g., overwrites existing transcript?), authorization needs, or rate limits. Adequate but not comprehensive.

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?

Two sentences with zero waste: first sentence states purpose and exceptions, second states a critical requirement. Front-loaded and efficient.

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, the description could mention what is returned after import (e.g., success status). However, the tool is simple and the description covers the core functionality well. Slight gap but overall complete for its context.

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?

Input schema has 100% coverage with descriptions for all properties and nested objects. The description emphasizes 'word-level timestamps' which is already in schema, adding no new semantic value. Baseline of 3 is appropriate as schema does the heavy lifting.

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?

Clearly states the action (import), the resource (external transcript), and distinguishes from transcription services by stating 'Skips Whisper entirely'. The verb 'import' and noun 'external transcript' are specific, and the description differentiates this tool from siblings like 'transcribe_start'.

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?

Explicitly says 'Skips Whisper entirely' (when not to use this tool) and requires word-level timestamps as a prerequisite. While it doesn't name alternatives directly, the context implies using 'transcribe_start' for Whisper-based transcription, providing clear usage context.

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