get_hunyuan3d_status

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

No annotations are present, so the description carries full behavioral burden. It does disclose the return type ('message indicating whether Hunyuan3D features are available') and frames this as a non-mutating check. However, it doesn't clarify whether the function ever enables anything, what happens if Blender isn't running, or what the message structure looks like. Acceptable baseline disclosure, but with no annotations, more depth would help.

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 front-loaded sentences, zero wasted words. The description efficiently conveys the check subject, the environment, and the output behavior.

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 the tool's low complexity (one assertion, simple message return, no output schema, no nested objects), the description covers the essentials: what's checked and what's returned. The completeness is dragged down by the completely unexplained user_prompt parameter, which an agent must somehow resolve. Adequate but with a visible gap.

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 description coverage is 0% and the description makes no mention of the user_prompt parameter, whose purpose is genuinely confusing for a status check. An agent given this description cannot tell whether to provide a prompt, why it defaults to an empty string, or what behavior changes if it's populated. Since the schema provides no help and the description adds zero clarification, this is a significant failure.

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 uses a specific verb ('Check') and resource ('Hunyuan3D integration in Blender') and clearly distinguishes this from sibling tools like get_hyper3d_status and get_polyhaven_status by naming the specific integration. The outcome ('whether Hunyuan3D features are available') makes the tool's scope unambiguous.

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 purpose implies this is a pre-flight check before using Hunyuan3D generation features, giving clear contextual timing. However, there's no explicit when-to-use-vs-alternatives guidance, and no mention that siblings like poll_hunyuan_job_status serve a different phase of the workflow. The usage context is implied rather than stated.

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