system_reload_integration

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 states 'reload' implies a mutation but does not disclose behavioral traits such as whether it requires permissions, potential side effects (e.g., brief service interruption), or whether the operation is reversible. The description lacks essential 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?

The description is a single short sentence, front-loaded with the action and resource. However, it is overly terse and sacrifices necessary detail for brevity. It earns its place but could be expanded without losing conciseness.

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 low complexity (one required parameter) and the presence of an output schema, the description is too minimal. It does not explain the result of reloading (e.g., success/failure indication) or any associated context like when this operation is needed. The tool's integration with other system operations is not addressed.

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 description coverage is 0%, meaning the input schema provides no explanation for the 'entry_id' parameter. The description does not clarify what the entry_id represents (e.g., the config entry ID from the integrations page) or how to obtain it. The parameter is semantically ambiguous.

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 the resource ('specific integration config entry'). It distinguishes from sibling tools like system_reload_all (reloads everything) and automations_reload_automations (reloads automation configs). However, it could be more precise about what reloading entails (e.g., forces re-reading of config).

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 such as system_reload_all or automations_reload_automations. No context on prerequisites or scenarios where reloading a specific integration is appropriate.

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