ssh_group_manage

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

No annotations are provided, so the description carries full responsibility. It explicitly discloses local-only persistence, no remote side effects, and that list is read-only with derived groups not editable here. This adds important behavioral context beyond a simple 'manages groups' statement, though it stops short of describing return values or error handling.

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 three sentences, densely packed with essential information: core purpose, operation list, parameter requirements, read-only caveats, and optional behavior. It is front-loaded and every sentence adds value, with no redundant or filler 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 (six actions, seven parameters, no output schema), the description covers the critical aspects: what each action does, per-action parameter requirements, local vs remote effects, and the derived-group nuance for list. It doesn't detail return values, but for a configuration management tool the description is sufficient for correct invocation.

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?

The input schema covers all parameters with descriptions (100% coverage), so the baseline is 3. The description adds meaningful conditional semantics: 'Every action except list requires name; add-servers and remove-servers also require a non-empty servers array' and explains that optional parameters set default execution behavior. This goes beyond the schema by linking parameters to specific actions.

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 identifies the tool as managing named server groups for ssh_execute_group, listing the specific actions (create, update, delete, add-servers, remove-servers, list) and scope (local configuration only). This distinguishes it from sibling tools like ssh_execute_group or ssh_list_servers.

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 notes that groups are 'used by ssh_execute_group', providing context for when to use this tool. It also explains the special read-only behavior of list for derived groups and clarifies that derived groups change via SSH configuration editing. While it doesn't explicitly state exclusions like 'use ssh_execute_group for execution', the related sibling is named and the role is clear.

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