get_blender_version

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

With no annotations, the description must carry the behavioral burden. It implies a read-only operation but does not explicitly state it. It also does not disclose any side effects, error conditions, or prerequisites. The description is minimal and does not add context beyond the return values.

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, concise sentence that gets straight to the point. It is front-loaded with the key information and contains no filler. Ideal for a simple getter.

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 trivial getter with no parameters and no output schema, the description is mostly complete. It states what data is returned but does not describe the format or structure (e.g., string vs object). Since there is no output schema, this is a minor gap, but the tool is simple enough that an agent can infer.

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, so the schema covers all (100%). The description correctly avoids parameter details. Baseline for 0 params is 4, and there is nothing to add.

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 returns Blender version, build, and Python version. It is a noun phrase but unambiguous. It distinguishes itself from other getters like get_bridge_status or get_scene_info by specifying exactly what data is returned. No ambiguity.

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?

No explicit guidance is given on when to use this tool versus alternatives. There is no mention of conditions, exclusions, or related tools. Usage is implied by the name and description but not articulated, leaving the agent to infer.

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