get_video_job

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

Description indicates a read-only operation ('Return'). No annotations provided, but the description is minimally transparent. Lacks details on rate limits or permissions, which are reasonable for a simple getter.

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?

One short sentence that directly states purpose. No wasted words, but no structural elements (e.g., sections). Acceptable for a simple 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?

Given one required parameter and the presence of an output schema, the description adequately covers the tool's purpose. Does not elaborate on return format or errors, but the output schema presumably handles that.

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?

With 0% schema description coverage, the description adds no extra meaning to the 'job_id' parameter beyond its name and type. It does not explain format, origin, or constraints of the job ID.

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?

Description clearly states the verb 'Return' and resource 'Hunyuan job', specifying the output 'current state and metadata'. This differentiates it from sibling tools like list_video_models or estimate_video_job.

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?

Usage is implied: retrieve job status by job_id. However, no explicit guidance when to use vs alternatives, such as when a specific job's details are needed after submission.

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