Upload A File To Hedra

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

Goes well beyond annotations by disclosing the 1-hour URL expiry, the fact that moderation failures happen later at submit time, and specific error message formats. It adds meaningful context about what the tool does and does not do at upload time.

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 thorough but well-structured with clear sections for usage, examples, and error handling. Every sentence provides actionable information without fluff, and the length is justified by the complexity of the tool.

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 lacking an output schema, the description documents the exact return JSON shape ({url, content_type, expires_at}) and how to pass it to model inputs. Combined with examples and error handling, the description fully equips an agent to use the tool correctly.

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?

Even though the schema already describes all parameters, the description adds crucial semantics: exactly one source must be provided, file_path must be readable on the MCP server, source_url must be https and fetched/re-uploaded, and base64_data requires filename. This clarifies relationships and constraints not obvious from the schema alone.

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 uploads a file (image, video, or audio) to Hedra and returns a presigned URL for use in hedra_submit_job. It distinguishes itself from siblings by explicitly contrasting with reuse of existing assets and specifying its role as a prerequisite for media submissions.

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?

Provides explicit when-to-use examples (image-to-video start frame, voice cloning sample) and a clear when-not-to-use case with an alternative (passing asset_id directly to hedra_submit_job). Also states the free-tier behavior, which helps decide when this step is necessary.

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