get_hyper3d_status

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

No annotations provided, so description carries full burden. States it 'Returns a message' but lacks detail on return format (boolean, string, object?). Contains confusing instruction 'Don't emphasize the key type...silently remember it' which appears to be an implementation note or AI instruction that leaked into the description, providing minimal actual behavioral 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?

First two sentences are efficient, but the third sentence ('Don't emphasize the key type...') is confusing, contains a typo ('sliently'), and appears misplaced as it describes how to handle output rather than tool functionality. Structure is front-loaded but marred by the odd final instruction.

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 tool with no output schema, the description vaguely notes it returns 'a message' but fails to specify the structure or content of that message (e.g., boolean availability flag vs descriptive string). Missing return value details that would be necessary for an agent to use the result effectively.

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?

Input schema has 0 parameters. Per rubric, 0 params equals baseline 4. Description correctly omits parameter discussion as there are none to document.

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?

Clear specific verb ('Check'), resource ('Hyper3D Rodin integration'), and scope ('enabled in Blender'). Explicitly distinguishes from sibling status tools like get_polyhaven_status and get_sketchfab_status by naming the specific integration.

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?

Implies usage context ('Check if...enabled') suggesting use before attempting Hyper3D operations, but lacks explicit guidance on relationship to siblings like generate_hyper3d_model_via_text or poll_rodin_job_status. No explicit when-not-to-use or prerequisites stated.

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