xae_restart_twincat

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

Annotations already flag destructiveHint=true and non-idempotent, so the 'Destructive-class' label largely repeats structured data. The description does add real behavioral context — the runtime restarts in RUN mode on the current target — but omits impact/downtime, permission needs, and how the confirm token gates execution.

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?

One compact sentence with the action front-loaded; no filler. Slight waste in 'Destructive-class,' which restates the destructiveHint annotation.

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?

An output schema exists so return values need not be described, but for a destructive restart of an industrial runtime the definition leaves key operational facts unexplained: the confirm-token requirement, downtime/state loss, and how to recover if the restart fails.

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?

There is one parameter (confirm_token) with 0% schema description coverage, so the description carries the full burden and says nothing about it. Given a sibling tc_request_confirmation exists, the omission of how the token is obtained and whether it is optional is a real gap.

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?

Names the verb (restart) and the resource (TwinCAT runtime) and clarifies the target scope (current target). It is distinguishable from build/deploy/mode-setting siblings, though the odd casing of 'StartRestartTwinCAT' and the 'XAE' prefix add noise rather than precision.

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 statement of when to use this versus alternatives such as tc_set_mode, ads_system_mode, or xae_activate_configuration. No mention of preconditions (confirmation flow, project attachment) or when not to call it.

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