drive_account_list

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

With no annotations, the description carries the full burden. It states 'Read-only, no parameters' and 'Never returns a secret', clearly indicating safe behavior. It also lists the output fields. It doesn't mention edge cases like missing files, but for a simple list command this is adequate.

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 well-structured sentence that front-loads the purpose, then adds output details, usage guidance, safety, and a CLI mirror. Every clause adds value, though it is slightly verbose; still efficient.

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 tool with no output schema, this description is remarkably complete: it details the source file, exact fields returned, usage order, safety guarantee, and CLI equivalent. An agent can invoke it correctly without additional context.

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 an empty schema. The description explicitly confirms 'no parameters' and mentions the configuration file as the implicit source, which is a baseline of 4 for parameterless tools. No further semantic detail needed.

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 verb 'List', the resource 'Drive accounts', and the specific location (settings.json). It enumerates the exact fields returned and distinguishes itself from siblings by noting it is the first step to discover valid account values before using drive_search/drive_file_read/drive_auth_status.

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?

Explicitly instructs when to use: 'Call this first to discover valid account values before passing one to drive_search/drive_file_read/drive_auth_status.' It also notes the tool is read-only and never returns secrets, providing safety context for decision-making.

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