list_groups

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

The description repeats the readOnlyHint but adds meaningful context beyond it: the list depends on the configured API key's user account and the resulting group IDs can be used in a downstream mutation tool. It also clarifies the scope (user's groups vs. server's configured library). These details are not present in the annotations alone, though pagination/ordering are not mentioned.

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 two sentences with no redundancy. The first sentence states the purpose directly, and the second sentence adds a practical cross-tool usage hint. It is front-loaded and every word contributes value.

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 list tool with an output schema and clear annotations, the description covers the essential aspects: purpose, read-only nature, user scope, and a key downstream integration. Nothing critical is missing given the tool's simplicity and the presence of structured metadata.

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 zero parameters, so the schema coverage is 100% by default and the baseline is 4. The description implicitly references the API key as a contextual input, but since no parameters exist, there is nothing more to document. It correctly avoids inventing parameter semantics.

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 states the tool lists Zotero groups belonging to the configured API key's user account, using the specific verb 'List' and identifying the resource. It also distinguishes this from sibling list tools (e.g., list_collections, list_tags) by focusing on groups and the authenticated user's membership.

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 a concrete usage pattern: passing each result's `id` to move_item_to_different_library when the desired group isn't the server's own configured library. This gives clear context for when the tool is useful, though it does not explicitly state when not to use it or name alternative tools for listing similar resources.

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