set_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 of behavioral disclosure. It only says 'Change' and does not disclose whether the theme is fully replaced or merged, whether unspecified properties are preserved, whether changes persist, or what side effects occur for an invalid slug or theme.

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, direct sentence with no filler or repetition. The action and target are front-loaded, making it easy for an agent to process quickly.

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?

The output schema means return values need not be described, and the theme schema provides a concrete example. Still, the description omits important invocation context such as whether the provided theme replaces existing settings or merges with them, and there are no annotations to cover mutation caveats.

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 description maps the theme object to understandable concepts: 'accent colours' covers accent/accent_soft and 'default light/dark mode' covers dark_default. However, it does not explain the slug parameter, and with only 50% schema description coverage, it only partially compensates for the schema's gaps.

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 states a specific action ('Change') and a precise resource: the site's accent colours and default light/dark mode. This distinguishes it from the sibling site tools such as get_site, render_site, delete_site, and update_meta, leaving no ambiguity about what set_theme does.

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 intended use is implied by the wording: use this when you need to change theme-related appearance settings. However, there is no explicit statement about when not to use it or which alternative tool (e.g., update_meta) should be chosen for other site metadata changes.

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