blender_status

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

No annotations are provided, so the description carries full burden. It describes a read-only operation but does not disclose behavioral traits such as whether Blender must be running, latency of connection check, or side effects (none expected). The description is insufficiently transparent for a tool with no 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 a single sentence, front-loaded with the main action. It is concise with no extraneous text. However, it lacks any structural elements like bullet points or additional sentences that might improve clarity for the parameter.

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 simplicity of the tool and the presence of an output schema, the description is adequate in scope but lacking in detail. It mentions three pieces of info (connection status, path, scene summary) but does not differentiate from similar tools like get_scene_info or scene_stats. The output schema likely covers return values, so completeness is moderate.

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?

Schema description coverage is 0%, and the description does not mention the port parameter at all. The agent is not told what the port is for (e.g., Blender server port). The description adds zero meaning beyond the schema for this parameter, which is unacceptable given the low coverage.

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 verb 'Check' and the resources 'Blender connection status, executable path, and scene summary'. It is specific and distinguishes from sibling tools like get_scene_info by focusing on connection and executable path.

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 does not state prerequisites (e.g., Blender must be launched) nor exclusions. The implied usage is checking before other operations, but this is not explicit.

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