groups_update

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

Annotations already indicate a write operation (readOnlyHint=false). The description adds the 'Replace' verb and PUT method, which implies full overwrite. However, it does not disclose idempotency, permissions, or error behavior. Some value added but not rich.

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 a single short sentence, which is efficient. However, it lacks depth that could be added without significant bloat. Still, no wasted words.

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?

With a mutation tool that has an output schema, the description does not explain when to use it vs. groups_patch, what the response entails, or any prerequisites. It is insufficiently complete for an agent to make informed decisions.

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%, so parameters are already well-described. The description does not add any additional meaning or usage context beyond what the schema provides (e.g., 'SCIM group ID', 'Full SCIM group body'). Baseline 3 applies.

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 replaces a SCIM group using the PUT HTTP method. This specific verb-resource combination distinguishes it from siblings like groups_create (create) and groups_patch (partial update).

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 implies full replacement via PUT, but does not explicitly state when to use this tool over alternatives such as groups_patch or groups_create. No exclusions or context are provided.

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