services_reload_config

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

With no annotations, the description carries full burden. It only says 'Reload configuration' without disclosing effects (e.g., disrupts running processes, requires authentication, reverts changes). The examples help but lack behavioral context.

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?

Single sentence front-loaded with purpose and examples. No extraneous text. Efficiently conveys the core action and resource type.

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 simple tool with one parameter and an output schema, the description covers basic purpose but lacks behavioral details and clear differentiation from siblings. The output schema exists but is not leveraged to describe return values.

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 0%, but the description adds meaning by listing example domain values (automation, script, scene, etc.), helping the agent understand what 'domain' refers to. However, it does not define the parameter explicitly or its expected format.

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 configuration') and the resource ('domain'), with specific examples like automation, script, scene, input_boolean. This distinguishes it from sibling tools that target specific domains (e.g., automations_reload_automations), as this is the generic version.

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 implies the tool is for reloading configuration of any domain, but it does not explicitly compare to sibling reload tools for specific domains (e.g., automations_reload_automations, helpers_reload_helpers). No guidance on when to use this vs alternatives, leaving the agent to infer.

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