Get upload instructions for media files (audio, images, video). Returns the upload URL and required headers. Requires API token authentication.
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | Filename for the upload | |
| type | No | Media type: audio, image, video, or text | |
| mime_type | No | MIME type of the file |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Given the readOnlyHint annotation, the description adds useful context by clarifying that this tool returns upload instructions (URL and headers) rather than performing the upload itself, and that authentication is required. This goes beyond the annotation without contradiction, though it omits rate limits or error behavior.
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 three concise sentences, each adding distinct value: purpose, return value, and authentication. No filler or repetition of the tool name.
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?
For a tool with no output schema, the description covers the core return value and auth, but lacks detail on possible error responses, URL expiration, or other edge cases. It also omits the 'text' media type from the schema, leaving a minor gap. Adequate but not fully complete.
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 already documents all three parameters with 100% coverage. The description adds marginal context by listing example media types (audio, images, video) but omits 'text' and does not enhance parameter understanding beyond the schema. Baseline 3 is appropriate.
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 function—getting upload instructions for media files and returning the upload URL and headers—with a specific verb and resource. However, it does not explicitly distinguish from sibling tools by naming alternatives, which prevents a perfect score.
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 only mentions API token authentication as a prerequisite, but offers no guidance on when to use this tool versus alternatives or when not to use it. The intended usage is only implied by the purpose statement.
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.
Every tool targets a distinct action or resource. Groups like compels, lighting cues, webhooks, and account are clearly separated, and even similar tools (create_compel vs create_compel_from_music) have well-defined differences in input source.
All tool names follow a consistent verb_noun pattern with underscores (e.g., cancel_compel, launch_lighting_cue, register_webhook). No mixing of conventions or ambiguous verb choices.
With 30 tools, the server is above the 25+ threshold for 'too many'. While the scope includes multiple subdomains, the high number adds cognitive load and risks selection errors for an agent.
Core workflows are present (create, read, cancel, list, search, render), but missing update/delete for compels and media, and no way to modify render configuration beyond defaults.