video_semantic_query

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

The description discloses that the tool does not invent descriptions, which is a key behavioral trait. However, without annotations, it lacks details on safety, permissions, or side effects. It adequately signals a read-like operation but is minimally informative.

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. It efficiently conveys the core action. However, its brevity comes at the cost of leaving out important parameter details, making it slightly less effective than it could be.

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 the complexity (nested object parameter, output schema exists) and lack of schema documentation, the description is severely incomplete. It fails to explain what the request should contain, what the output represents, or how the tool fits into a workflow.

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 input schema has 0% description coverage as it only defines a single 'request' object with additionalProperties. The description does not explain what properties should be included in the request, nor does it clarify the expected structure. This provides no help beyond the 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 states a specific verb and resource: 'Query source-backed semantic spans locally'. This clearly indicates the tool's function. However, it does not explicitly differentiate from sibling tools like 'video_semantic_timeline', though the mention of 'locally' provides implicit distinction.

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 given on when to use this tool versus alternatives. The phrase 'without inventing descriptions' hints at a constraint, but there is no explicit context for appropriate usage scenarios.

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