Manage User Group

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

The description adds idempotency behavior details beyond annotations, such as returning 'already_exists' for duplicate add. However, it does not disclose behaviors for 'update' or 'remove' actions, leaving gaps. Annotations already provide idempotentHint=true, so additional value is modest.

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 extremely concise with two front-loaded sentences. The first sentence captures the purpose, and the second provides key behavioral detail without any filler.

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 has 6 parameters and no output schema, the description covers idempotency but lacks details on update/remove behavior, the routerId parameter, and dryRun effects. While schema covers param descriptions, the description could be more complete for operational understanding.

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% with clear descriptions for all parameters. The description adds semantic context by explaining how the 'name' and 'policy' parameters interact with idempotency, enhancing understanding beyond the schema alone.

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 explicitly states the verb (Add, update, remove) and resource (local RouterOS user group). It clearly distinguishes the tool's purpose from siblings like manage_user, making it easy to understand what the tool does.

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 mentions idempotency behavior for 'add' but does not provide explicit when-to-use guidance or differentiate from sibling tools like manage_user. The context of usage is implied rather than directly stated.

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