execute_on_group

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key traits: parallel execution, timeout behavior, fail-fast option, and return format ('formatted summary of results'). It doesn't mention authentication requirements, rate limits, or error handling specifics, but covers the essential operational behavior.

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 perfectly structured and front-loaded: the first sentence states the core purpose and key characteristic, followed by well-organized parameter documentation in a clear Args/Returns format. Every sentence adds essential information with zero wasted content.

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?

Given the tool's complexity (parallel execution across servers), absence of annotations, and presence of an output schema, the description provides complete context. It covers purpose, parameters, behavioral characteristics, and references to sibling tools. The output schema handles return value details, so the description appropriately focuses on operational context.

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?

With 0% schema description coverage, the description fully compensates by providing clear explanations for all 5 parameters. Each parameter gets specific semantic context: 'group' references sibling tool usage, 'command' clarifies it's a shell command, 'timeout' specifies per-server behavior and default, 'working_dir' explains remote execution context, and 'fail_fast' defines failure handling logic.

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 specific action ('Execute a shell command'), target resource ('on all servers in a group'), and key behavioral characteristic ('parallel execution'). It distinguishes from sibling tools like 'execute' (single server) and 'list_groups/list_servers' (read-only operations).

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 provides clear context for when to use this tool (parallel execution across server groups) and references 'list_groups' as a prerequisite for discovering available groups. However, it doesn't explicitly state when NOT to use it or compare it to alternatives like 'execute' for single-server operations.

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