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 indicating availability, which is useful. However, it doesn't describe error conditions (what happens if Blender isn't running), performance characteristics, or whether this is a lightweight check versus a heavy operation. The cryptic note about 'Don't emphasize the key type...' adds confusion rather than clarity about behavior.

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 reasonably concise (three sentences) but has structural issues. The first two sentences clearly state purpose and return value. The third sentence ('Don't emphasize the key type...') is confusing and doesn't add value to tool understanding - it appears to be implementation notes rather than user-facing documentation. This reduces effectiveness despite brevity.

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 zero parameters, no annotations, and no output schema, the description provides basic but incomplete context. It states what the tool checks and what it returns (a message), but doesn't describe the message format, possible values (enabled/disabled/error), or how to interpret results. For a status-checking tool with no structured output documentation, more detail about return values would be helpful.

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 schema description coverage is 100% (empty schema). The description appropriately doesn't discuss parameters since none exist. It focuses correctly on what the tool does rather than parameter details, earning a baseline 4 for zero-parameter tools.

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: 'Check if Hyper3D Rodin integration is enabled in Blender' (specific verb+resource). It distinguishes from siblings like get_polyhaven_status or get_sketchfab_status by specifying the Hyper3D Rodin integration. However, it doesn't explicitly contrast with other status-checking tools beyond 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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., whether Blender must be running), when this check should be performed (before attempting Hyper3D operations), or what to do based on the result. The only implicit usage is checking Hyper3D Rodin availability, but no explicit when/when-not/alternatives are provided.

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