update_service_group

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

No annotations are provided, so the description carries the burden. It does add one genuinely useful behavioral detail, that `members` replaces the existing list, and returns a status/message dict. However it says nothing about required permissions, ADOM locking, reversibility, or what happens to omitted fields, which is a meaningful gap for a mutation tool without annotations.

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?

One-line purpose followed by an Args block and a Returns block; every line carries content and the purpose is front-loaded. Nothing is padded or repetitive.

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?

For a four-parameter mutation tool with no annotations this is only adequate: the parameters are covered, but call prerequisites (locking the ADOM, whether the group must already exist) are unstated. The Returns section is redundant given an output schema already exists.

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 description coverage is 0%, so the description must compensate, and it does: all four parameters get short glosses, including the important semantic note that `members` replaces rather than appends. It stops short of specifying whether members are object names or references, but it adds real meaning beyond the bare titles.

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 a specific verb and resource ("Update a service group") and enumerates the fields that can be changed. It does not distinguish this tool from siblings such as update_address_group, create_service_group, or delete_service_group, so an agent gets a clear purpose but no sibling routing help.

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?

There is no guidance on when to use this tool versus create_service_group, get_service_group, or the address-group equivalents. No prerequisites (e.g., ADOM lock, existing group requirement) or exclusions are given; the description is purely a field list.

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