get_hunyuan3d_status

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

With no annotations provided, the description bears the full burden of behavioral disclosure. It states the tool returns a message about availability, which implies read-only behavior, but it does not explicitly confirm no side effects, mention possible errors, or describe what happens if the integration is disabled. This is adequate but minimal for a simple status check.

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 concise, two clear sentences with no extraneous words. It front-loads the core purpose and states the return type, making it efficient and easy to parse.

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?

While the tool is simple, the presence of an undocumented user_prompt parameter creates a significant gap. The description does not explain the parameter's role or provide enough context for correct invocation. Additionally, the description only vaguely mentions 'a message' without detailing the output structure, even though an output schema exists. The overall completeness is lacking for a tool with an unexplained parameter.

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 input schema includes one parameter, user_prompt, with a default empty string, and schema description coverage is 0%. The description does not mention this parameter at all, leaving it completely unexplained. Why a status check needs a user prompt is unclear, and the agent has no information on how to fill or use it. The description fails to compensate for the schema's lack of documentation.

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 checks whether Hunyuan3D integration is enabled in Blender, naming the specific integration and distinguishing it from sibling status tools like get_hyper3d_status and get_sketchfab_status. The verb 'check' and resource are explicit, leaving no ambiguity about the tool's function.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., before generating a Hunyuan3D model) or when not to use it. The description implies a status check but does not state any prerequisites, exclusions, or conditions for selection, leaving the agent to infer usage from context.

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