blender_get_version

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

With no annotations provided, the description carries the burden of behavioral disclosure. 'Get' implies a read operation, but the description does not state that the tool is non-mutating, what it returns, or whether anything in Blender may change. This is a very thin transparency layer.

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 a single clear sentence with no filler or redundancy. It is front-loaded and appropriately sized for a zero-parameter getter, earning its place without wasting tokens.

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 tool is simple, but the description does not clarify what result is returned, such as a version string, an integer, or a structured object. Since there is no output schema, the description carries some responsibility for specifying the return shape. It is sufficient for a quick invocation but not 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 tool has zero parameters and a 100% schema coverage for that empty schema, so there are no parameter semantics to describe. The baseline of 4 is appropriate because the description cannot add value on parameters that do not exist.

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 uses a specific verb and resource: 'Get Blender version information.' It is clear and distinguishes this from the many scene/object/render siblings, though it largely restates the tool name and does not clarify what the version information contains beyond the name.

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 or when-not-to-use guidance, and no alternatives are named. The intended usage is only implied: call this when you need Blender's version. Because it is a simple zero-parameter probe, the omission is not critical, but the guidance is still only implicit.

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