account_list

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

With no annotations, the description carries the transparency burden. It discloses that each profile has its own quota and specifies the return fields (profile, account, authenticated, default). It also notes that adding accounts requires a separate CLI command, providing operational context beyond a simple list operation.

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?

Three sentences, front-loaded with the main purpose. Every sentence earns its place: the first states what it does, the second explains the profile/quota context, and the third provides the alternative for adding accounts. No filler.

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 no parameters, an output schema exists, and the description covers return fields and usage context, the tool is fully specified. The quota note adds useful operational context, and the CLI guidance fills a likely user need.

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 baseline is 4. The description adds no parameter-specific details because none are needed; the schema is already empty and complete.

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 ('Lista') and clearly identifies the resource ('cuentas de Google (perfiles) disponibles para NotebookLM'). It distinguishes itself from sibling tools like account_use by focusing on listing available profiles rather than using them.

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 clarifies that this tool is for listing accounts and provides an explicit alternative workflow for adding accounts via a CLI command. While it doesn't mention sibling alternatives like account_use, the instruction to run `notebooklm login` for adding implies this tool is not for that purpose.

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