BlenderMCP

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool returns a message about feature availability, which is helpful, but lacks details on potential errors, latency, or side effects. For a status-checking tool, this leaves gaps in understanding how it behaves in different scenarios.

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 extremely concise and well-structured, with two sentences that directly state the action and the return value. Every word serves a purpose, and it's front-loaded with the core functionality, making it easy to parse quickly without any fluff.

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?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is adequate but minimal. It covers the basic purpose and return type, but for a status-checking tool, it could benefit from more context on what the returned message entails or potential use cases, leaving some gaps in completeness.

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 tool has 0 parameters, and the input schema has 100% description coverage, so there are no parameters to document. The description appropriately doesn't waste space on parameter details, earning a high score for not adding unnecessary information beyond what the schema already covers.

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's purpose with a specific verb ('Check') and resource ('PolyHaven integration in Blender'), making it immediately understandable. It distinguishes itself from siblings like 'get_hyper3d_status' by specifying the PolyHaven integration, though it doesn't explicitly differentiate from other status-checking tools beyond naming the target.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, such as whether Blender needs to be running or configured, or suggest when to use it over other status-checking tools like 'get_hyper3d_status' or 'get_sketchfab_status' in the sibling list.

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