blend-ai

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While it mentions the tool 'Sets' something (implying mutation), it doesn't describe permissions needed, whether changes are reversible, or any side effects. The return format is mentioned but lacks detail about error conditions or confirmation content.

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 appropriately brief and front-loaded with the core purpose. The Args and Returns sections are structured clearly, though the initial sentence 'Set the render engine.' could be slightly more informative (e.g., specifying it's for the active scene).

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 tool has an output schema (returns confirmation dict) and only one parameter with full semantics provided in the description, the description is reasonably complete. However, for a mutation tool with no annotations, it could better address behavioral aspects like what happens if an invalid engine is specified or if no scene is active.

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 description adds significant value beyond the input schema, which has 0% description coverage. It explicitly lists the valid enum values for the 'engine' parameter (BLENDER_EEVEE_NEXT, CYCLES, BLENDER_WORKBENCH), which the schema only indicates as a string type without constraints.

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 'Set' and the resource 'render engine', making the purpose understandable. However, it doesn't explicitly differentiate this from sibling tools like 'set_render_resolution' or 'set_render_samples', which are related but distinct render configuration tools.

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 provided about when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., whether a scene must be open), nor does it explain the relationship with other render-related tools like 'render_image' or 'render_animation'.

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