get_hyper3d_status

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

No annotations are provided, so the description carries the burden of disclosing behavior. 'Check if ... enabled' strongly implies a read-only status check and it says a message is returned, but it does not explicitly state that it is side-effect-free or clarify whether it checks local Blender state, an external service, or something else.

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 two short sentences with no filler. It front-loads the verb and resource, and the second sentence adds the return behavior without redundancy.

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?

The output schema presumably covers the return message, so the main gap is the undocumented user_prompt parameter. Combined with the absence of annotation context and any routing guidance among the many similar status tools, the description is not fully complete for correct invocation.

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 single parameter user_prompt has 0% schema description coverage and is not mentioned in the description at all. The agent has no way to know what this parameter means, whether to pass it, or how it affects the status result.

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') with a specific resource ('Hyper3D Rodin integration in Blender') and names the observable outcome ('returns a message indicating whether features are available'). This clearly differentiates it from siblings like get_hunyuan3d_status or get_polyhaven_status.

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 this tool should be used before relying on Hyper3D Rodin features, but it never explicitly says when to use it versus the other status tools or the Hyper3D generation tools. There is no when-not guidance or mention of alternatives.

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