Get Blender Agent Context

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

No annotations are supplied, so the description carries the full burden, yet it never says whether this is a pure read, whether it mutates session state, whether it requires an active Blender connection, or roughly how much text it returns for 'compact'. The word 'compact' is the sole nod to output size, and 'public' is unexplained.

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?

A single front-loaded sentence with no padding or redundancy. It is efficient, though its brevity borders on under-specification rather than tightness.

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 zero-argument context loader the description should say what the agent receives and how it relates to the bootstrap sibling, especially since there is no output schema. It is minimally viable but leaves the agent guessing about the return payload and the sequencing.

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 zero parameters at 100% coverage, so there is nothing for the description to disambiguate. Baseline 4 applies for a no-parameter tool.

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 verb 'Load' and the object 'operating rules' give a rough sense of the operation, but 'compact ViperMesh operating rules' and 'persistent Blender MCP sessions' are product jargon that an agent cannot resolve from the text alone. It does not distinguish this from the sibling bootstrap_vipermesh_session, which plausibly loads overlapping session material.

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?

There is no explicit when-to-use, when-not-to-use, or ordering guidance, and with siblings like bootstrap_vipermesh_session, check_blender_connection and list_blender_tools in the same family, the agent has no basis to pick this one first. 'Persistent Blender MCP sessions' is the only contextual hint and it is not framed as a condition.

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