set_group

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

Annotations already declare idempotentHint=true and destructiveHint=false, so the bar is lower, but the description adds real value: it states the operation does not touch the request/workflow content and that an empty group un-assigns it, which is the key reversibility behavior.

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?

Three short sentences, front-loaded with the action and target, with no filler. The reassignment and removal semantics are captured without repetition.

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?

An output schema exists so return values need no explanation, and the description covers the non-destructive nature and the un-grouping case. It omits only edge behavior such as what happens to a group with no remaining members.

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%, so all three parameters are already documented. The description reinforces the empty-string behavior of `group` and gives example values, but adds little the schema does not already say — 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 ('file ... under a group') and names the exact resources affected — a saved request or a workflow — and clarifies it does not modify the resource itself. It is unambiguous, but it never differentiates itself from siblings like save_request or set_variable by name.

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?

'Use it to tidy the Saved list' implies the organizing context but gives no explicit when/when-not or alternative tools. The inclusion of the empty-group removal case is helpful, yet the agent must infer usage conditions.

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