winops_accounts_list_groups

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the return format ({"success": bool, "raw_output": str}), providing some value beyond annotations, though it doesn't elaborate on error conditions or scope of enumeration. No contradiction exists between description and 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?

The description is efficiently structured: a one-sentence core purpose, a clearly formatted return-format section, and a usage example. Every section earns its place. Minor blemish: the example function name 'list_groups()' doesn't match the tool's actual name 'winops_accounts_list_groups', though this is a minor style issue.

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 zero-parameter listing tool with strong annotations and an existing output schema, the description covers the essentials: what it lists, its return shape, and how to call it. Nothing critical is missing given the tool's simplicity, though it could note any default enumeration limits or independence from domain joins.

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 tool has 0 parameters with 100% schema coverage, so the description doesn't need to explain parameters. The example 'list_groups()' reinforces the no-argument call signature, meeting the 0-parameter baseline of 4.

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 'List local Windows groups.' uses a specific verb ('List') with a clear resource scope ('local Windows groups'), and the qualifier 'local' helps distinguish it from siblings like winops_accounts_list_users and winops_accounts_group_members. It's clear and unambiguous, though it doesn't explicitly name alternatives for differentiation.

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 provides zero when-to-use guidance, no context on when to prefer this over winops_accounts_group_members or winops_accounts_list_users, and no exclusions or alternatives. The usage is only implied by the verb and resource, matching the 'no guidance' description.

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