preview_group_update

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

With no annotations, the description must disclose behavior, but it simply restates the tool's purpose. It does not indicate that previewing is non-destructive, what side effects exist, or what the output represents, leaving the agent without crucial behavioral information.

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 short and contains no filler, but it is so minimal that it borders on under-specification. It is concise but does not use the space to provide valuable context, making it less useful than a slightly longer description.

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's complexity (two parameters, one being an open object) and the absence of annotations and output schema, this description is grossly insufficient. It leaves critical questions unanswered about what constitutes a valid update, how the preview is returned, and whether it validates constraints.

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?

The schema has zero coverage for groupId and updates, and the description does not explain these parameters. updates is an arbitrary object with no structure described, so the agent has no idea what fields or format to use. The description fails to compensate for the missing schema documentation.

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 identifies the tool as previewing a site group update, using a specific verb and resource. It distinguishes from siblings like apply_group_update and preview_list_update by naming 'group', but lacks detail on what the preview entails.

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 preview versus apply_group_update, nor any context about prerequisites or workflow. The description provides no cues about appropriate vs. inappropriate usage scenarios.

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