zerodom_list_groups

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

With no annotations, the description carries the full burden. It meaningfully discloses persistence across restarts and the behavioral implication of an empty list (sandbox off; unrestricted tabs), which is valuable context beyond the schema. It does not describe read-only safety or return shape, but the output schema covers the latter.

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?

Two sentences, front-loaded with the primary action and followed by the key edge-case interpretation. Every sentence earns its place and there is no redundant text.

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-argument list tool with an output schema, the description supplies what is needed: what is listed, that it is persisted, and how to interpret the empty result. No missing operational context prevents correct invocation.

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?

There are zero parameters, so per the scoring rule this is the baseline 4. The schema is empty and the description has no parameters to clarify, so no gap exists.

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 and resource: 'List the agent's named tab groups (its sandbox).' The parenthetical defines the resource and distinguishes it from tab-level siblings like zerodom_list_tabs, and 'as remembered across restarts' adds scope.

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 second sentence gives interpretation for an empty result ('No groups → the sandbox is off and the agent can drive any tab'), which implies the tool can be used to check sandbox state. However, it does not explicitly say when to call this versus alternatives such as zerodom_list_tabs or zerodom_create_group, leaving usage context implied rather than stated.

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