list_groups

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that the output includes members and access state, which is useful context beyond the annotations, but it does not discuss the nature of the data (e.g., static snapshot, live state, formatting).

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 compact phrase with no filler. It is front-loaded with the resource, though as a fragment it lacks a clear verb that would make it immediately scannable as an action.

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?

The tool has no parameters and an output schema, so the description need not explain return values. However, it does not say what a 'group' represents, how many groups might be returned, or how this listing relates to sibling tools like access_status, leaving a gap for the agent.

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?

Zero parameters, so there is nothing to document. The baseline for a parameterless tool is 4, and the description does not contradict or undercut that.

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 names a resource ('device groups') and hints at scope ('with their members and current access state'), but the verb is implicit and the phrase is a noun fragment rather than a complete purpose statement. It does not distinguish itself from siblings like access_status or list_devices, leaving the agent to infer that this is a listing tool.

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?

No when-to-use guidance, exclusions, or alternatives are provided. The agent is not told whether to call this before set_group_membership or set_access, or how it differs from access_status.

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