zones_reload_zones

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

With no annotations, the description carries full burden. 'Reload' implies re-reading configuration, but it does not disclose potential side effects (e.g., overwriting existing zones, impact on active automations, error handling). Minimal information beyond the basic operation.

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 extremely concise—single sentence with no extraneous words. Every word ('Reload', 'zones', 'from YAML', 'via service zone.reload') carries essential information. Appropriately sized for a simple action.

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?

Despite having an output schema (which reduces the need to explain return values), the description lacks critical context: what triggers a reload, whether it requires a specific file, behavior on error, and relationship to other zone operations. For a system action, more completeness is warranted.

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 no parameters, so the description does not need to add parameter detail. However, it adds meaning beyond the empty schema by specifying the source (YAML) and service. This is a reasonable baseline for a parameterless tool.

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 the action (reload) and resource (zones from YAML). It specifies the underlying service (zone.reload). While it doesn't explicitly differentiate from other reload tools, the tool name and context make the purpose sufficiently clear.

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?

No guidance on when to use this tool versus alternatives like zones_create_zone, zones_update_zone, or other reload tools (e.g., automations_reload_automations). The description does not provide context for when a reload is appropriate.

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