BlenderMCP

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool checks integration status and returns a message, but lacks details on permissions, rate limits, error handling, or what the message format entails. The cryptic note about 'Don't emphasize the key type...' adds confusion rather than clarity, failing to compensate for the missing annotations.

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 relatively concise with two main sentences, but the second sentence about 'Don't emphasize the key type...' is vague and doesn't add value, reducing efficiency. It could be more front-loaded by starting with the core purpose without the cryptic note.

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 low complexity (0 parameters, no output schema, no annotations), the description is minimally adequate. It explains what the tool does and the return type (a message), but lacks context on integration specifics or error cases. Without annotations or output schema, it should provide more behavioral detail to be fully complete.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add param info, which is appropriate, earning a baseline 4 for not introducing unnecessary details. It avoids redundancy with the schema.

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.' It specifies the verb ('Check') and resource ('Hyper3D Rodin integration'), and distinguishes it from siblings like 'get_polyhaven_status' or 'get_sketchfab_status' by focusing on Hyper3D Rodin. However, it doesn't explicitly differentiate from all siblings (e.g., 'get_object_info' or 'get_scene_info'), so it's not a perfect 5.

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, context, or exclusions, such as whether it should be used before other Hyper3D-related tools or in specific Blender states. With no usage instructions, it relies on the agent to infer from the purpose alone.

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