Reload themes from disk

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

Annotations already declare idempotentHint=true, destructiveHint=false and readOnlyHint=false, giving the safety profile. The description adds real substance beyond that: it names the underlying service (frontend.reload_themes) and the scope of the reload (every YAML file under <config>/themes/), which tells the agent the effect is broad and system-wide. It stops short of noting limits like error handling on malformed YAML.

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?

Front-loaded with the core action, then systematically structured into 'Use when' and 'Returns' blocks. Every sentence carries distinct information (scope, underlying service, trigger conditions, return value) with no repetition.

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 no-param reload tool with an output schema, the description covers purpose, mechanism, triggers and even the return shape. An agent has everything needed to decide when to call it and what to expect.

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 takes zero parameters, so there is no parameter semantics to document; the description correctly supplies none and instead focuses on behavior. Baseline 4 for a no-param tool is appropriate.

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?

States a specific verb and resource ('Reload theme files from the themes directory') and elaborates on what reloading actually means: re-reading every YAML file under `<config>/themes/`. This clearly distinguishes it from sibling themes_create_theme/update/delete and from themes_list_themes, which read rather than reload.

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?

Provides an explicit 'Use when' clause covering both trigger conditions: after a create/update/delete that wrote with reload=False, or after editing a theme file outside the toolset. It names the specific sibling tools whose effects it complements, leaving little to inference.

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