update_vulnerability_group

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered structurally. The description adds a genuinely non-derivable operational fact: the server-side WRITE_ENABLED gate that will reject the call. It omits partial-update semantics (whether omitted fields are preserved), which is the main remaining behavioral question for a mutation of this kind.

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?

A single front-loaded clause names the entity, the lookup key, and the mutable surface, with the write gate appended as a clear bracketed condition. There is no filler, and the most actionable constraint (WRITE_ENABLED) is impossible to miss.

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 six fully documented parameters, an annotation set covering safety and idempotency, and no output schema to explain, the description supplies everything needed to attempt the call. The only gap is the partial-vs-full update behavior, which an agent would need to know before sending a subset of fields.

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 100%, with sys_id length, state enum codes, and date format all documented in the schema itself. The description only names the field categories ('state transitions, (re)assignment, target date'), adding no format or constraint detail beyond what is already structured. 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?

States a specific verb and resource ('Update a Vulnerability Group') and pins the key identifier ('by sys_id'), then enumerates the mutation categories it accepts. It does not explicitly distinguish itself from the close sibling update_vulnerability, which operates on a different entity, leaving the agent to infer the boundary from the name alone.

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 gives one useful precondition — 'requires WRITE_ENABLED=true' — which tells the agent when the call is permitted to succeed. It never states when to prefer update_vulnerability (single item) over update_vulnerability_group, nor any exclusions such as closed groups being immutable, so routing between siblings is only implied by naming.

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