cueprecise_excerpt

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

The description discloses the truncation behavior and the need to advance the start value, which is a key behavioral trait. Since no annotations are provided, the description carries the burden, and it does well by revealing this non-obvious behavior, though it does not explicitly state whether the operation is read-only.

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 exceptionally concise, using just two sentences to convey purpose, output contents, truncation behavior, and continuation strategy. No superfluous words or redundant explanations are present.

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 description gives enough context for an agent to understand the basic invocation and output type (subtitles and frames), but it omits details like time units, frame format, and the exact output structure. Given that no output schema is defined, a bit more detail would improve completeness, but it is still adequate for a basic call.

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?

The description only indirectly references the 'start' parameter in the truncation note, while 'video_id' and 'end' are not explained at all. With zero schema-level descriptions and no parameter annotations, the description fails to convey the meaning or units of these parameters, leaving the agent to guess.

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: retrieving subtitle text and frames for a specified time interval. It uses a specific verb ('조회한다') and resource ('자막 원문과 프레임'), and the truncation note helps distinguish it from related tools like cueprecise_frames or cueprecise_query.

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 provides explicit usage guidance for handling truncated results by moving the start parameter to continue fetching, which is actionable. However, it does not explicitly compare with sibling tools or state when to choose this over alternatives, so it loses a point.

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