app-addon_disable

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

There are no annotations provided, so the description carries the full burden of behavioral disclosure. It only states the action without mentioning side effects, reversibility, idempotency, or whether the module must currently be enabled. This leaves the agent without insight into the tool's operational impact.

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 clear sentence that is front-loaded and contains no filler or redundant content. Every word contributes meaning.

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?

For a mutation tool with no annotations, no output schema, and a single parameter, the description is too minimal. It does not explain what happens after disabling, whether the module must exist, or how to discover candidate module ids. The sibling tool app-addons might be relevant but is not mentioned.

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 schema has a single 'module' parameter with title 'Add-on module id', and the description adds almost no meaning beyond that. It says 'installed' but does not explain how to obtain valid module ids, expected format, or relationship to listed add-ons. With 0% schema description coverage, the description fails to compensate.

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 uses a specific verb ('Disable') with a clear resource ('installed Blender add-on module'), making the tool's function immediately obvious. It also distinguishes itself from the sibling tool app-addon_enable by explicitly stating the disabling action.

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 usage context is implied by the name and description: use this when you need to disable a Blender add-on. However, it provides no explicit guidance on prerequisites, when to prefer this over other tools, or how to locate the correct module id before disabling.

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