List Blender Tools

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

With no annotations, the description carries the full behavioral burden and discloses almost nothing: it does not say the call is read-only, whether 'trusted local portable gateway' implies an auth/connection prerequisite, or whether results are cached or paginated. The single useful signal is that execute_code is exposed for fallback measurement.

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?

One compact sentence with no filler, and the core purpose is front-loaded. It is short to the point of under-specification rather than wordiness.

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 discovery tool with no output schema, no annotations, and two undocumented parameters, the description should at minimum explain what the listing returns (names only? schemas?) and how query/category narrow it. Neither is covered, leaving an agent unable to predict the response shape.

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 says nothing about the two optional parameters, query and category, such as whether they filter by name, substring, or exact category value. The agent must guess the filtering semantics entirely from bare property names.

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?

States a specific verb and resource ('List Blender commands available through the trusted local portable gateway') and even names one returned item, execute_code. It does not distinguish itself from close siblings like call_blender_tool or check_blender_connection, so it falls short of a 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?

There is no statement of when to call this versus call_blender_tool, call_blender_tool_batch, or check_blender_connection. The only hint is the parenthetical 'for fallback measurement' attached to execute_code, which does not tell an agent when to prefer this listing tool.

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