blender_addons

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only mentions that 'list_installed' requires Blender, but fails to specify prerequisites, side effects (e.g., enabling/disabling modifies Blender state), or authorization needs for install/uninstall operations.

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 front-loaded with a clear statement of purpose and a concise list of operations. Every sentence serves a purpose, with no redundant information.

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?

While the description covers all operations, it lacks detail on error handling, return values (though an output schema exists), and consistent prerequisites (only 'list_installed' mentions 'requires Blender'). It is adequate but not comprehensive for a tool with six parameters and multiple operations.

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 coverage is 100%, so the baseline is 3. The description adds some value by mapping operations to parameters (e.g., 'install_addon: Install from local addon_path'), but does not provide significant additional meaning beyond the schema's parameter descriptions.

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 'Manage Blender addons' and lists all operations, making the purpose explicit. It also distinguishes from the sibling tool 'manage_blender_addons' by claiming preference, which helps an agent choose correctly.

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?

The description explicitly says 'Prefer this tool over manage_blender_addons', providing direct guidance on when to use this tool versus a sibling. The list of operations further clarifies the scope of use.

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