list_blender_commands

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

With no annotations provided, the description carries the entire burden of behavioral disclosure. It only states that it lists commands, but says nothing about side effects (e.g., read-only), output format, or any operational nuances. For a listing tool this is a significant gap.

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 with no redundancy. It is immediately front-loaded with the core action and resource, achieving maximum clarity in minimal space.

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 no-argument listing tool with an output schema, the description is minimal but arguably adequate. However, it omits any context about when to prefer this over the many similar listing tools, and it does not hint at the shape of the grouping. Given the breadth of siblings, a bit more context would be expected.

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 the schema is empty, which matches the baseline of 4. The description does not need to add parameter context because there are none, and it introduces no confusion.

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 a specific verb (List), a resource (dedicated Blender Studio Pro MCP commands), and a distinguishing organization (grouped by module). It is specific enough to separate it from many siblings, though it does not explicitly contrast with the similarly named list_dedicated_commands, so it misses full differentiation.

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 guidance is given about when to use this tool versus alternatives like list_dedicated_commands, list_operator_categories, or list_tool_categories. The description only states what it does, leaving selection entirely to inference.

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