app-addons

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

With no annotations, the description carries the full burden. It transparently states that it lists add-ons and includes their enabled and loaded state, indicating a read-only operation with no side effects. This is sufficient for a simple listing tool, though it doesn't specify whether built-in vs. third-party add-ons are included or if there are any filters.

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 that fully conveys the tool's function without any redundancy or unnecessary detail. It is efficiently structured and front-loaded with the action and resource.

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 simplicity of the tool (no parameters, no output schema, no annotations), the description fully covers what the tool does and what it returns. There are no missing behavioral aspects or edge cases that need documentation for a basic list operation.

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 with 100% coverage. The description correctly adds no parameter details since none exist. Per the rubric, a baseline of 4 is appropriate for tools with no parameters, as no additional parameter semantics are needed.

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 'List available Blender add-ons with enabled and loaded state' clearly states the action (list), the resource (Blender add-ons), and the specific data provided (enabled and loaded state). This distinguishes it from sibling tools like app-addon_enable or app-addon_disable, which perform mutations.

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 implies its use for inspecting add-on states but does not explicitly compare to alternatives or specify when to use it (e.g., before enabling/disabling). While the purpose is obvious from the name, there is no explicit guidance on when to choose this over related tools like app-addon_enable or app-preferences_summary.

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