hyperframes_transcribe

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

No annotations are provided, so the description carries the full behavioral burden. It does not disclose whether transcription writes files, whether existing files are replaced, what permissions or model prerequisites are needed, or how import mode differs behaviorally from transcription. The overwrite safety detail lives only in the schema and is not surfaced in the description.

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 front-loaded sentence with no wasted words. Its brevity is efficient, though it borders on under-specification rather than polished concision. It is structurally sound but thin.

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?

With 5 parameters, low schema coverage, no annotations, and two apparent modes, the definition is not complete enough for reliable invocation. Although an output schema exists and need not be explained, critical gaps remain around parameter effects, file handling, and mode selection. The description does not do enough to make the tool safely callable.

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 only 20%, so the description should compensate for undocumented parameters like model, language, input_path, and project_path. Instead it adds no per-parameter meaning and does not explain how those parameters affect transcription, import, or project placement. It only hints at output granularity (word-level timestamps), leaving most parameter semantics unexplained.

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 states a specific verb and resource: transcribe audio/video into word-level timestamps, or import transcripts. That is clear enough to know what the tool does. However, it does not differentiate from close siblings such as video_ai_transcribe, video_generate_subtitles, or video_subtitles, so an agent cannot tell when this tool is the right one without inspecting schemas.

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 phrase "or import transcripts" hints at two modes but never states when to choose transcription versus import. There is no guidance on when to use this instead of sibling tools like video_ai_transcribe or video_generate_subtitles. No exclusions, prerequisites, or context cues are provided.

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