get_hunyuan3d_status

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

With no annotations, the description carries the full burden. It discloses that the tool returns a message indicating availability, which is useful, but it does not explicitly state whether the operation is safe/read-only or mention any side effects. Given the word 'Check' implies a read-only action, this is adequate but not rich.

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 clear, front-loaded sentences with no wasted words. The description states the action and the return behavior succinctly, appropriate for a simple status 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?

For a simple status check with no output schema or annotations, the description covers the core purpose and return type, but leaves gaps: the user_prompt parameter is unexplained, and the exact nature of the 'message' is vague. Enough for basic use, 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 schema has a single parameter, user_prompt, with 0% schema description coverage, and the description does not mention it at all. This is a significant gap: the tool's purpose is a status check, and the parameter seems unrelated. The description provides no meaning for the parameter.

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 clearly identifies the resource ('Hunyuan3D integration') and context ('in Blender'). It distinguishes the tool from sibling status checks like get_hyper3d_status by explicitly naming Hunyuan3D.

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 implies usage as a pre-flight check for Hunyuan3D features, but does not explicitly state when to use it versus alternatives, nor does it mention any prerequisites or exclusions. The intent is clear but not directly stated.

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