gcloud_auth_list

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

With no annotations, the description carries full responsibility for behavioral disclosure. It accurately describes a read-only listing operation (no destructive side effects), but does not disclose details like whether the active account is returned as part of the list or separately, what the output format is (since no output schema), or whether this command requires prior authentication.

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 with no wasted words. It front-loads the primary action ('List') and adds a secondary action ('show the active account'), covering the tool's core functionality efficiently.

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?

Given the tool has zero parameters, no output schema, and no nested objects, the description is complete enough for the tool's simplicity. It fully explains what the tool does without requiring additional elaboration.

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 and 100% schema description coverage, so the schema provides full parameter information. The description meaningfully adds context by specifying what the tool returns ('all authenticated accounts' and 'the active account'), increasing agent understanding beyond the bare schema.

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') and clearly identifies the resource ('authenticated accounts'), plus adds a distinct action ('show the active account'). This distinguishes it from siblings like gcloud_auth_login and gcloud_auth_print_access_token, as listing accounts is a different operation.

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 implies usage for viewing current authentication state (listing accounts, showing active), but does not provide explicit guidance on when to use this versus alternatives like gcloud_auth_print_access_token or gcloud_auth_login, nor when not to use it. The context is clear but lacks exclusions or decision rules.

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