video_semantic_timeline

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

The description implies a constructive action ('Build'), but with no annotations, it fails to disclose side effects, authorization needs, or what 'local' means. The brevity leaves significant behavioral ambiguity.

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?

While concise, the single sentence is under-specified given the complexity of the tool (free-form object input, output schema). It lacks necessary detail to be effective.

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?

Despite an output schema, the description omits crucial details about input structure, the nature of 'analyzer evidence', and what 'local, source-time' entails. Incomplete for a tool of this complexity.

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 single parameter 'request' has no schema description (0% coverage), and the description does not clarify its expected structure or fields. The tool adds no semantic value beyond the bare schema.

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 action ('Build') and the resource ('semantic timeline'), with qualifiers 'local, source-time' and 'from supplied analyzer evidence'. This distinguishes it from siblings like 'video_semantic_query' and 'video_timeline_edit_plan', though not explicitly.

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?

No guidance is provided on when to use this tool instead of alternatives, nor any context on prerequisites or typical use cases.

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