quote_demo_videoFree preview of assemble_demo_video pricing. Sums the Hume Octave narration cost across segments and adds a flat 10-credit assembly fee. Useful before committing to a longer video.
| Name | Required | Description | Default |
|---|---|---|---|
| segments | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | No | Tool result payload (JSON object) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds value by explaining the pricing logic (sums Hume Octave narration cost, adds flat 10-credit assembly fee) and explicitly states it is a 'free preview', which is not in annotations.
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, no unnecessary words. Front-loaded with the key purpose. Every sentence adds value: first sentence states purpose, second gives usage hint.
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 presence of an output schema covers return values, and annotations cover safety. However, the lack of parameter descriptions in both schema and tool description leaves a gap for the agent to understand the required nested fields, making it slightly incomplete.
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 schema has 0% description coverage for the single 'segments' parameter, which is a complex array of nested objects. The description does not explain the structure or meaning of the nested fields, relying entirely on the schema which lacks descriptions.
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 'quotes' the credit cost for a 'multi-segment demo video', using specific verbs and resources. It differentiates from sibling tools like 'assemble_demo_video' by indicating this is a pricing preview.
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 usage context: 'Useful before committing to a longer video', implying it should be used before assembly. However, it does not explicitly state when not to use it or list alternatives beyond the implied assembly tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
The tools cover a wide range of functionalities, but each has a clearly distinct purpose. For example, submit_test, submit_test_batch, submit_combo, and submit_interaction_scene are all different types of submissions with unique parameters. However, the sheer number of tools (43) might cause some initial confusion, but descriptors resolve ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., list_projects, create_project, get_test_results). The only exception is 'whoami', which is a common idiom and does not break the pattern. Overall, naming is highly predictable.
43 tools is on the high side for a single server. The domain is broad (testing, worker marketplace, credits, cards, feedback, video), so the count is justifiable. However, it borders on being overwhelming, and some tools could be consolidated (e.g., multiple submit_* variants).
The tool surface covers core workflows like project creation, test submission, result retrieval, worker management, and credit operations. However, there are gaps: no update or delete for projects, no delete for worker offerings, and no user-facing combo editing (though combos are predefined). These are minor but noticeable.