blender_addons

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

Annotations provide no safety hints (all false), so the description carries the burden. It discloses that list requires Blender and describes operations, but doesn't specify side effects like network access, file deletion, or config changes. It gives basic behavioral context but lacks depth.

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 structured with an introductory purpose sentence and a bulleted operation list. It is slightly long but information-dense; no wasted words. The redundant list_addons/list_installed pair is minor.

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?

With a complex operation set and output schema present, the description covers all main operation categories and parameter mappings. It notes Blender requirement and known registry, but could mention enable_on_install behavior or error scenarios. Still nearly complete for selection and invocation.

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 provides descriptions for all parameters (100% coverage), but the description enriches them by mapping operations to specific parameters (e.g., install_from_url uses addon_url, install_addon uses addon_path). It also clarifies 'install_known' and 'search' semantics beyond the schema.

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?

Description clearly states the tool manages Blender addons and enumerates specific operations (list, install, uninstall, enable/disable, search, info). It explicitly distinguishes itself from sibling manage_blender_addons with 'Prefer this tool over manage_blender_addons.'

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 advises preference over manage_blender_addons, which serves as an alternative. The operation list provides clear context for which action to invoke, mapping operations to parameters.

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