ssh_group_manage

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

With no annotations, the description must disclose behavioral traits, but it simply says 'manage' without explaining side effects (e.g., if delete is irreversible, if updates are partial) or required permissions. This is insufficient for safe tool invocation.

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 very concise (one sentence) but fails to list all actions, sacrificing completeness for brevity. It could be improved by front-loading the complete list of actions.

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 schema has 7 parameters with mixed purposes (management vs execution), the description is too vague. It doesn't explain the connection between actions and execution-related parameters, nor does it describe return values or output behavior.

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?

Although schema coverage is 100%, the description adds no extra meaning. Crucially, the parameters 'strategy', 'delay', and 'stopOnError' appear related to execution (not group management) but lack explanation in the description, causing confusion about their role.

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 states the tool manages server groups with actions like create, update, delete, list, but fails to mention 'add-servers' and 'remove-servers' actions present in the schema. This omission makes it incomplete and could mislead an agent about available 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?

No guidance is provided on when to use this tool versus sibling tools like ssh_execute_group. An agent has no context to decide between managing group definitions or executing commands on a group.

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