xae_command

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

Annotations already declare destructiveHint=true, so the bar is lower, yet the description adds real value by defining which command names fall into the destructive class. It does not, however, explain what confirm_token is for or what triggers a confirmation requirement, leaving a behavioral gap for a destructive-capable tool.

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?

Two dense sentences with no filler, and the core action is front-loaded ahead of the classification rule. Slightly clunky punctuation around "(e.g. 'PLC.Login'). Control-class;" but nothing wasteful.

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 generic, destructive-capable command executor with 0% parameter documentation, the description should explain how args are passed and when confirm_token is required. The output schema covers return values, so that omission is acceptable, but the input-side gaps are significant.

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% across three parameters, and the description only implicitly touches 'name' via an example. The format of 'args' (a free-form string — quoting, separators, positional ordering) and the purpose/requiredness of 'confirm_token' are entirely undocumented in both schema and description.

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+resource: 'Execute an arbitrary DTE command', with a concrete example ('PLC.Login'). It is clearly distinguishable from xae_list_commands (which enumerates) and from typed siblings like xae_build or xae_plc, though it never names those alternatives explicitly.

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 destructive-class naming heuristic (download/reset/activate/restart/delete/remove/shutdown) implicitly tells the agent when an operation is risky, which is genuine contextual guidance. However, there is no guidance on when to prefer this raw escape hatch over typed siblings such as xae_build, xae_activate_configuration, or xae_restart_twincat, and nothing about prerequisites.

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