poll_hunyuan_job_status

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

Describes states (DONE, RUN) and return data (ResultFile3Ds with ZIP path) in detail. Also notes it is a polling API. With no annotations, this offers good transparency.

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?

Mostly concise with a clear structure (parameters, returns). Minor redundancy with the header 'For Hunyuan3D:' but overall well-organized.

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 simple schema and no annotations, the description covers the parameter, expected states, and return data adequately. Could note failure states but still sufficient.

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?

Schema coverage is 0%, but the description explains job_id is 'The job_id given in the generate model step,' adding necessary context beyond the schema's minimal 'Job Id' title.

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?

Clearly states it checks if Hunyuan3D generation is completed, specifying verb and resource. However, it does not distinguish from sibling tool 'get_hunyuan3d_status', which likely performs a similar check.

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 usage context: 'This is a polling API, so only proceed if the status are finally determined.' But no guidance on when to use this vs alternative tools like get_hunyuan3d_status or poll_rodin_job_status.

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