remote_command_group_run

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It does reveal the dry_run behavior and the session/connection choice, but it omits critical traits such as side effects, permissions, potential destructiveness, or what happens after execution. For an execution tool, this is a significant gap.

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 exceptionally concise: two short sentences and a fragment, every part earning its place. The purpose is front-loaded, followed by essential usage detail. No redundant words or fluff.

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, the tool is complex (9 parameters, 2 required) with no annotations. The description does not explain the core parameters (`group`, `action`) nor how they relate to the 'specialized action' concept. It lacks essential context for correct invocation, making it incomplete for this complexity level.

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%, so the description must explain parameters. It clarifies the relationship between session_name and profile/connection, and defines dry_run's effect. However, the required parameters `group` and `action` are not described at all, leaving the agent without enough context to fill them correctly. Other optional parameters like `timeout`, `parameters`, and `output_limit` also lack explanations.

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 tool's purpose: 'Build and run a specialized action' with concrete examples (user management, services, reboot, system inventory). It uses a specific verb and resource, which distinguishes it from generic execution tools, though it does not explicitly name sibling alternatives.

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 gives minimal usage hints: 'Use either session_name or profile/connection' and explains dry_run, but it does not specify when to choose this tool over similar siblings like remote_execute or remote_run_script. There is no explicit when-to-use or when-not-to-use guidance, making it hard for an agent to select this tool correctly.

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