gws.accounts.list

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

The description adds context about the output (labels and default status) beyond the readOnlyHint and destructiveHint annotations. However, it does not disclose any additional operational behavior such as pagination, sorting, or error conditions. With annotations already establishing the read-only nature, the description adds moderate value.

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 a single sentence of 12 words, front-loaded with the verb 'list' and the resource. Every word contributes meaning, with no fluff or repetition.

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 operation with clear annotations and distinct sibling tools, the description fully covers what the tool does and what it returns. Although there is no output schema, the description explicitly mentions the return content ('labels and default status'), making it complete for a tool of this complexity.

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 is fully covered by default. The description appropriately does not attempt to explain parameters; it would have been redundant. This aligns with the baseline for parameterless tools.

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 uses a specific verb 'list' with a clear resource ('connected Google Workspace accounts') and specifies the returned details ('labels and default status'), clearly distinguishing it from account mutation tools like gws.accounts.add or gws.accounts.remove.

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?

Usage is implied: you would use this tool when you need to see all connected accounts. However, the description does not explicitly mention when to use it over alternative tools, nor does it provide any exclusions or prerequisites.

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