get_polyhaven_status

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

The description indicates a read-only check ('Check if' and 'Returns a message') without stating side effects or permissions. Since no annotations are present, it partly relies on implication, but it is likely safe.

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 sentences with no redundant information. It efficiently conveys the tool's purpose and output.

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 description covers the core function and return type (a message) but omits details about the output format and the meaning of the user_prompt parameter. The overall context is incomplete for a full understanding.

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 sole parameter 'user_prompt' has no description, and its purpose is entirely unclear. The schema provides no details, and the description does not mention it, leaving it unexplained and likely unused.

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 it checks if PolyHaven integration is enabled in Blender, which is specific and distinct from other status tools like get_hyper3d_status or get_sketchfab_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 when to use it (when checking PolyHaven availability) but does not explicitly contrast with alternatives or provide conditional guidance. It is somewhat clear but lacks explicit direction.

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