ssh_group_manage

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

Without annotations, the description discloses key behaviors: 'persisting changes to local configuration only with no remote side effects', action-specific requirements, and that optional parameters set 'default group execution behavior'. Lacks details on return values or error handling, but adequate for a management 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?

Four sentences, no redundancy, well-structured with the main purpose first, then action details, then parameter constraints. Every sentence adds necessary information without waste.

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?

No output schema exists, but the description does not mention what the tool returns (e.g., for 'list' action, a list of groups; for create/update/delete, confirmation). Also lacks error scenarios and details on persistence longevity. For a tool with 7 parameters and multiple actions, this is a significant gap.

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 coverage is 100%, and the description adds value by explaining which actions require which parameters (e.g., 'servers' must be non-empty for add-servers/remove-servers) and that strategy/delay/stopOnError set default behavior. This goes beyond the schema's basic descriptions.

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 'creates, updates, deletes, and inspects named server groups' and explicitly ties it to 'ssh_execute_group', distinguishing it from siblings that execute commands or list servers. The verb 'manage' is substantiated by listing specific actions.

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 details which action requires which parameters ('Every action except list requires name; add-servers and remove-servers also require a non-empty servers array') and notes that 'list is read-only'. Missing explicit guidance on when to use this tool versus alternatives like ssh_list_servers, but the context is clear.

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