activate_theme

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

No annotations are provided, so the description carries the full burden. It clearly discloses that this tool changes what visitors see and is the go-live step. It does not mention permissions or rate limits, but it sufficiently describes the behavioral impact for a simple activation tool.

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 paragraph with three sentences, front-loaded with the main action. Every sentence adds value with no unnecessary text.

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 simple one-parameter tool with an output schema, the description is complete: it explains purpose, usage guidelines, and provides a cross-reference. The output schema covers return values, so no further detail is needed.

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% (one required parameter 'name' is described). The description adds a helpful cross-reference to list_themes, aiding discoverability. Beyond that, it does not add syntax or format details, but the baseline of 3 is elevated due to the useful reference.

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 'Activate an installed theme, making it the LIVE theme. Changes the site.' This provides a specific verb and resource, and distinguishes it from sibling tools like upload_theme or preview_theme by emphasizing the go-live step.

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 'Call it ONLY on the user's explicit instruction to activate a specific theme -- never as an automatic follow-on...' and explains that upload installs inactive, so activation is a separate deliberate step. This provides clear when-to-use and when-not-to-use guidance.

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