blender_setup

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

Reveals important side effects beyond the annotations: the addon is copied into Blender's user addons directory, Blender itself enables and saves the preference, other add-ons are left untouched, and the bridge starts only after a restart. These details give the agent a correct mental model of a mutating setup step.

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?

Four focused sentences, front-loaded with the one-line purpose followed by when, what happens, and what to do next. Every sentence adds behavioral value and none repeats the schema.

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?

Covers purpose, trigger, mechanics, non-destructiveness, and post-condition, which is unusually complete for a setup tool. It could additionally state the expected success output, but there is no output schema and the operational flow is already clear.

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 does not mention either parameter. Schema coverage is only 50%: response_format is described, but enable_addon has only a title/default; the description should have clarified per-parameter behavior, especially what enable_addon=false means.

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?

Opens with a specific action and resource: 'Install the bundled Blender addon and enable it' and ties it to starting the bridge. The description also gives a precise invocation condition via blender_status, which separates this tool from the many scene/object manipulation siblings.

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?

Explicitly says 'Call this ONCE on a machine where blender_status reports not connected' and tells the user the necessary follow-up: restart or launch Blender. This is a clear when-to-use rule even without a competing setup sibling.

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